University of Edinburgh

_______________________________________________________________________________________________________

Stage: Acceptance

User Acceptance Test (UAT) Plan

http://www.mitsubishielectric.com.sg

Document Version: 1.2

Date: 9/2/07

___________________________________________________________________________________

Management Information Services - Template Revised October 2004

Acceptance: User Acceptance Test Plan [Project Name]
[Version: x.x]
_______________________________________________________________________________________________________

Contents

1 DOCUMENT MANAGEMENT........................................................................3
1.1 Contributors...........................................................................................................3
1.2 Version Control.......................................................................................................3

2 USER ACCEPTANCE TESTING ...................................................................4

2.1 User Acceptance Definition...................................................................................4
2.2 UAT Responsibilities..............................................................................................4

3 UAT STRATEGY.............................................................................................5

4 USER TESTING.............................................................................................6

5 UAT RESULTS...............................................................................................9
5.1 Open Issues.............................................................................................................9
5.2 Document Sign Off.................................................................................................9

___________________________________________________________________________________

Page 2 of 9
Acceptance: User Acceptance Test Plan [Project Name]
[Version: x.x]
_______________________________________________________________________________________________________

1 Document Management
When completing this document, please mark any section that is not required as
‘N/A’. A brief description of why the section is not required should also be included.

1.1 Contributors
Please provide details of all contributors to this document.

Role Department Name

Owner ‘N/A’ Notionage
Contributor Web Development Min Soe Han Win
Contributor ISS(Mitsubishi) Veronica
Contributor ISS(Mitsubishi) Sung Kit
Contributor

1.2 Version Control

Please document all changes made to this document since initial distribution.

Date Version Author Section Amendment

23/04/08 1.0 Leonard Create document
28/05/08 1.1 Min Soe Han Add New Information
Win

___________________________________________________________________________________

Page 3 of 9
Acceptance: User Acceptance Test Plan [Project Name]
[Version: x.x]
_______________________________________________________________________________________________________

2 USER ACCEPTANCE TESTING

2.1 User Acceptance Definition

The UAT for http://www.mitsubishielectric.com.sg website will be broken down into

two sections namely front-end UAT and back-end UAT. This document is to ensure
that the CMS web development service that Notionage Pte. Ltd. provided met the user
requirement as in the agreement.

2.2 UAT Responsibilities

Role Name Responsibilities

Account Manager Clara Leo Communication with Customer to agree format and
scope of UAT

Agree acceptance criteria with the Customer prior to

commencing UAT

Ensure testing takes place within agreed timeframes

Programmer Min Soe Han Assist Customer with the creation of detailed test
Win plan and system documentation.

Programmer Min Soe Han Ensure that a detailed test plan is available for test
Win users

Ensure that bugs identified during UAT are logged in

the Test Log

___________________________________________________________________________________

Page 4 of 9
Acceptance: User Acceptance Test Plan [Project Name]
[Version: x.x]
_______________________________________________________________________________________________________

3 UAT STRATEGY
The User Acceptance Test Plan should be used to record the Customer’s sign off of the documented
scenarios. It is recommended that detailed test plans be used to record the results of user testing.

The document is a high level guide, and is not intended as a replacement for any specific user
acceptance testing procedures that individual areas might have.

Consideration Date Agreed Details

Test Approach
Assumptions & Constraints
Setup of Test Environment
Test Scenarios
Test Period

___________________________________________________________________________________

Page 5 of 9
Acceptance: User Acceptance Test Plan [Project Name]
[Version: x.x]
_______________________________________________________________________________________________________

4 USER TESTING
User testing should be based on the pre agreed test scenarios or acceptance criteria. It should be
noted if the scenarios have been sourced from the BRD, or if they have been identified subsequently.

Identified in BRD
Scenario Who Date Notes
Tested

Identified Post BRD

Scenario Date Notes
Tested
1. System Access
1.1 A user can log into the CM interface using EASE CM, 9/2/07 Was OK,
Richard Richard to
work on
1.2 The published web site can be accessed using a (test) CM Output
virtual server name template not
yet available
*
1.3 Pages on the published website can be accessed using CM Output
their “friendly URLs” template not
yet available
*
1.4 Images can be viewed as part of pages on the CM Output
published website template not
yet available
*
1.5 Files can be uploaded to articles using the CM interface CM Input
[this ensures that the firewall settings are correct] Richard template not
working –
minor fix
1.6 Files can be downloaded from the published website CM Output
template not
yet available
*
2. Communication
2.1 Content entered via the CM interface is saved in the CM 9/2/07 OK
database
2.2 Content published via the CM interface can be viewed CM Output
via the front servers template not
yet available
*
2.3 Updated content appears on the front servers within the CM Output
time dictated by the cache settings. template not
yet available
*
2.4 If the CM server is unavailable, the front servers CM Output
continue to serve content for ? hours template not
yet available
*
3. Performance
3.1 [no load - baseline] A request for a published page CM Output
should take no more than 0.5s template not
yet available
*
___________________________________________________________________________________

Page 6 of 9
Acceptance: User Acceptance Test Plan [Project Name]
[Version: x.x]
_______________________________________________________________________________________________________

3.2 [no load - baseline] A request for a page in the CM CM 9/2/07 OK

interface should take no more than 1s
3.3 performance testing under load N/A Part of
OTH050
project?
(Mark
Wetton is
organising
load test)
4. Backup
4.1 A suitable backup schedule is in place for the database PJ Nightly
backup in
place (TEST)
4.2 A suitable backup schedule is in place for the CM server PJ Nightly
backup in
place (TEST)
4.3 A suitable backup schedule is in place for the front PJ Nightly
servers backup in
place (TEST)
5. Logging
5.1 The Polopoly statistics server is operating correctly CM/RG 9/2/07 OK
5.2 The web server is logging page accesses PJ Apache web
server is
logging both
CM and
front-
endaccess
5.3 The log files as described at http://www- CM/RG 9/2/07 OK
dev.confluence.mis.ed.ac.uk/confluence/display/MIS/Logging
are working correctly
6. Functionality
6.1 The build tests for the local code project are successful CM In progress
(see separate document in project OTH050)
7. Indexing
7.1 The Lucene indexing service is working correctly CM/RG OK
8. Management
8.1 Suitable scripts are in place to start and stop Polopoly PJ Peter to
on the CM server and the front servers confirm
9. Monitoring
9.1 Service availability is being monitored and logged PJ MIS has no
functionality
to
automatically
detect
availability.
In LIVE the
UWS system
will be added
to the CSG
system
availability
monitoring
sheet

___________________________________________________________________________________

Page 7 of 9
Acceptance: User Acceptance Test Plan [Project Name]
[Version: x.x]
_______________________________________________________________________________________________________

9.2 Procedures are in place to alert the relevant people if PJ Same as

the service fails 9.1. If there
are no
automatic
scheduled
jobs the
system
owner is
responsible
to raise
service
failure as
descrbed in
SLA.

* The OTH050 project has not yet published data available (06-FEB-07). A template is being put
together by OTH050 project team for above tests.

Any issues identified during UAT should be added to the MIS Test Log. It may be agreed that UAT can
be signed off while some issues remain – please add the test log reference to the appropriate section
above if this is the case.

___________________________________________________________________________________

Page 8 of 9
Acceptance: User Acceptance Test Plan [Project Name]
[Version: x.x]
_______________________________________________________________________________________________________

5 UAT RESULTS

5.1 Open Issues

Please insert a copy of any open issues from the Test Log, together with details of why these issues
remain open at the sign off of the Acceptance Stage.

5.2 Document Sign Off

Business Project Manager Name

Project Manager Name

___________________________________________________________________________________

Page 9 of 9