Information Systems Services

User Test Plan Example

This document is an example User Test Plan and is intended for use in conjunction with the User Testing
Guidelines. The examples within are not comprehensive and form part of a fictitious scenario. If creating
a new user test plan for actual use, a blank template is available.

User Test Plan Example

Contents
1

Checklist ....................................................................................................................... 3

Test Environment.......................................................................................................... 4
2.1

Objective ................................................................................................................. 4

2.2

Test Data ................................................................................................................ 4

2.3

Data Migration ........................................................................................................ 4

2.4

Test Environment.................................................................................................... 4

Test Phases .................................................................................................................. 5

Test Scenarios .............................................................................................................. 6

Test Cases ................................................................................................................... 7

5.1

S1 - Accessing the system ..................................................................................... 7

5.2

S2 Product Maintenance ..................................................................................... 7

Test Scripts ................................................................................................................... 8

6.1

Scenario S1 Accessing the system...................................................................... 9

Remedial Actions Log ................................................................................................. 10

Record of final sign off ................................................................................................ 11

Information Systems Services

Page 2 of 11
Version 1.3

Document1

User Test Plan Example

1 Checklist
Action

Date required

Identify test owner

01/05

Identify staff to write test plans

01/07

Identify staff to write test scripts

01/07

Identify staff to perform testing

01/07

Define IT test environment

08/07

Define physical test environment (room etc.)

08/07

Write test plans

31/07

Write test scripts

31/10

Write data migration and validation scripts

14/10

Arrange physical test environment

31/10

Confirm IT test environment including data

10/11

Execute test scripts

15/11

Sign off system

29/11

Information Systems Services

Done?

Page 3 of 11
Version 1.3

Document1

User Test Plan Example

2 Test Environment

2.1 Objective
This test plan details the tests required to satisfy the project sponsor of the Online Shop
project that the changes implemented in support of this project are adequate to allow the
use of these changes in a production environment. Any deviations from expected system
behaviour which are not considered serious enough to prevent the changes from being
released for use are detailed in the Remedial Actions log.

2.2 Test Data

Specific data required for individual tests is detailed with the individual test scripts. Data for
the Banking test phase will be provided by Barclays as part of their standard testing suite
and the test scripts for this phase will be tailored to suit this data. Given the nature of the
Reporting test phase, a large amount of data will be required in the reporting test system.
This will need to be generated by IT staff as dummy data. The precise nature of this data
will again be detailed in the test scripts for this phase.

2.3 Data Migration

As all products in the online shop will need to be associated with suitable structures in the
corporate finance system, appropriate finance codes will need to be migrated into the live
system prior to the system going live. A separate test phase (P5 Data Migration) covers
this and will describe the precise data validation tests required to confirm this data has
been transferred correctly.

2.4 Test Environment

All tests will be carried out in the RX3 test environment. The database will not be cleansed
prior to testing for this project as any data resident in the system will be considered valid
data for the purposes of these tests.

Information Systems Services

Page 4 of 11
Version 1.3

Document1

User Test Plan Example

3 Test Phases
Phase

Description

P1

Shopping on the system

P2

Delivering the goods

P3

Banking

P4

Reporting

P5

Data Migration

Information Systems Services

Page 5 of 11
Version 1.3

Document1

User Test Plan Example

4 Test Scenarios

Scenario Name and Summary

No.

Test in
Phase

S1

P1

Accessing the system

Ensure that users can access the system and are only able to perform
functions appropriate to their role.

S2

Product maintenance

P1

Ensure that products (with all associated attributes) can added,

updated and removed from the system and assigned appropriately to
the product catalogue.
S3

Shopping

P1

Excluding banking
S4

Warehouse order receipting

P2

NOTE: Warehousing, stock control and distribution are outside

scope. Existing processes handle this so test will be limited to
receipt of order by the warehouse.
S5

Making a purchase

P3

S6

Reconciliation of bank reports

P3

S7

Managing refunds

P3

Etc

Information Systems Services

Page 6 of 11
Version 1.3

Document1

User Test Plan Example

5 Test Cases
5.1 S1 - Accessing the system
Test
Case
No.

Logical Tests

001

Can an administrator access the administration system

002

Can a non administrator user access the administration system

003

Can an administrator setup other administrators

004

Can a non registered user access the shopping system

005

Can a new user register onto the shopping system

006

Can a registered user access the shopping system from on-site.

007

Can a registered user access the shopping system from off-site.

5.2 S2 Product Maintenance

All tests refer to tests of the administrative system. Authorisation of access to this is tested
in scenario S1.
Test
Case
No.

Logical Tests

001

Can a user add a new product with the following attributes:

Product id
Product name
Product vat code
Product price

002

Can a user delete a product from the catalogue

003

Can a user update all attributes (except id) of a product for which no orders
have been placed

004

Can a user update products for which orders have been placed but not
delivered

005

Can a user update products for which there exist delivered orders but no nondelivered orders

006

Etc

Information Systems Services

Page 7 of 11
Version 1.3

Document1

User Test Plan Example

Test Case
ID

Step

001

Description

Can an administrator access the

administration system
Open internet explorer and navigate to
http://onlineshop/adminlogin

Expected Results

Actual Results /
Comments

Followup
Action

Test
Complete

Online Shop User Admin Page

displayed

001

Login as user user_admin1 using

appropriate password.

User login should be accepted and

administration home page should be
discplayed.

002

Can a non administrator user access

the administration system

User login should be rejected with the

message Unknown user. Access
denied.

OPEN

Open internet explorer and navigate to

http://onlineshop/login
Login as user user1 using appropriate
password.
003

Can an administrator setup other

administrators

User should login and navigate to Add

user page.

Open internet explorer and navigate to

http://onlineshop/adminlogin

All data should be entered OK and

clicking Save should return the user to
the admin home page.

Login as user user_admin1.

Click on add user

Setup proceeded OK but

administrator flag isnt set.

RL_S2_00
1

The user should be able to login to the

system as user_admin2 and be taken

Information Systems Services

Page 8 of 11
Version 1.2

Document1

User Test Plan Example

Enter details:

to the admin home page.

Name:user_admin2
Password: password
Admin role: Yes
Click Save.
Close browser
Open internet explorer and navigate to
http://onlineshop/adminlogin
Login as user user_admin2.

004

Etc.

6 Test Scripts
6.1 Scenario S1 Accessing the system
Ensure that users can access the system and are only able to perform functions appropriate to their role.
6.1.1 Pre-requisites
An administration user user_admin1 must exist on the system.
Non-administration user user1 must exist on the system.
There are no further data pre-requisites.

Information Systems Services

Page 9 of 11
Version 1.2

Document1

User Test Plan Example

7 Remedial Actions Log

This log contains details of elements of the system which either do not function according to agreed design, or which require
alteration due to a change in requirements. In each case, an agreed method of resolution is detailed.

Priority

Cost
K
Owner

Reason

Raiser

Action Description of change required

No.

Resolution

001

Current system is unable to record new

administrators. This is a system bug and needs
to be rectified.

Failure of test
S1-003

AB

PM

Low

002

Non admin users can access admin function.

Critical security breach must be prevented.

Failure of test
S1-002

TD

DE

High Immediate fix required.

003

Login screen not in corporate colours

Not in spec

TD

PM

10

Med Take to board for decision

Information Systems Services

Can be manually managed

by IT team, so bug fix can
wait until post go-live.

Page 10 of 11
Version 1.2

Document1

User Test Plan Example

8 Record of final sign off

The following people acknowledge that all tests detailed on this test plan have been either executed successfully, or had remedial
actions agreed. These signatures constitute agreement that the product if fit to release into production.

Name

Role

John Mulligan

Business Owner

Allan Benedictine

Tester

Jose Strickland

Tester

Tom Francis

Project Manager

Signature

Information Systems Services

Date

Page 11 of 11
Version 1.2

Document1