User Acceptance Test Plan - University of Edinburgh



[pic]

Stage: TEST Acceptance

User Acceptance Test (UAT) Plan

Technology Enhanced Learning (TEL):

Speedwell database hosting

TEL002

Document Version: 0.11.02

Date: 1115 February 201324/10/12

Contents

1 Document Management 3

1.1 Contributors 3

1.2 Version Control 3

2 User Acceptance Test 3

2.1 Definition 3

2.2 Roles and Responsibilities 3

2.3 Test Requirements 4

2.4 Test Participants 4

2.5 Test Schedule 5

2.6 Test scenarios and Acceptance Level 5

2.7 Assumptions 56

3 Acceptance Test Log 67

3.1 Test Scenarios –detailed steps 67

3.1.1 Test 1 67

3.1.2 Test 2 68

3.1.3 Final comment 78

4 Acceptance Test Results 78

4.1 Comments and feedback from UAT 78

4.2 Issues raised at UAT and follow up 79

4.3 Open Issues 79

4.4 Document Sign Off 79

Document Management

1 Contributors

|Role |Unit |Name |

|Project Manager |IS Applications |Franck Bergeret |

|Project Sponsor |MVM/Learning Technology |David Williamson |

|Business Lead |MVM Academic Administration |Neil McCormick |

| | | |

| | | |

| | | |

2 Version Control

|Date |Version |Author |Section |Amendment |

|15 Feb 13 |1.0 |Neil McCormick |

|Project Manager |Communication with the Business Lead and Business Assurance Coordinator to |Franck Bergeret |

| |agree format and scope of UAT | |

| |Ensure that UAT environment is ready | |

| |Ensure acceptance criteria are agreed prior to commencing UAT | |

|Business Lead |Assist Business Assurance Coordinator with the creation of a detailed test |Neil McCormick |

| |plan | |

| |Review scripts/cases and scenarios for accuracy, completeness and | |

| |sequencing. | |

| |Confirm test data is correct. | |

|Technical Architect |Validation of Test database environment |Riky Harris |

|Business Assurance |Ensure that a detailed test scripts/cases, scenarios and instructions are |Judi Bryce, Vanessa |

|Coordinator |available for test users prior to the start of testing |Feldberg, Julie Prentice, |

| |Ensure that issues identified during UAT are logged in the Test Log |Jennifer HillNeil |

| |Ensure testing takes place within agreed timeframes |McCormick, David Williamson|

|Testers |Execute test scripts/cases |Judith Bryce, Vanessa |

| |Document test results |Feldberg, Julie Prentice, |

| | |Jennifer HillNeil McCormick|

4 Test Requirements

• Testing will take place atin the MVM campus at Little France. Testers will perform the testing from their regular work location where it is possible.

• UAT testing window will be betweenwill take place on Thursday 21 February 2013 Wednesday 7th Nov and Wed 14th Nov 2012.

• Testing participants will receive instructions prior to the start of testing.

• Test scripts/cases and scenarios will be prepared prior to the start of UAT and will be listed in section 2.6 and 3.

• Test participants will conduct the tests and will document the results.

• Issues will be recorded in JIRA () and tracked by the Project Manager and Business Assurance Coordinator.

• The principal technical goal of the testing is to confirm that data entered using the Speedwell CliniQuest and QuestionBank software is recorded correctly in the database. The business goals are to ensure operation of the software overall is successful, which is a slightly wider scope.

5 Test Participants

Testing participants include representative from all areas involved in the solution. Testers and their specific areas of focus are identified in the following document:

|Full Name |Email Address |Title |Location |Pc or Mac |Additional Notes |

|Judi Bryce |Judith.Bryce@ed.ac.uk |MBChB Year 4 Co-ordinator |MVM Academic Administration |PC | |

|Vanessa Feldberg | |MBChB Year Co-ordinator |MVM Academic Administration | | |

|Julie Prentice | |Clerical Officer |MVM Academic Administration | | |

|Jennifer Hill | |MBChB Year Co-ordinator |MVM Academic Administration | | |

|Neil McCormick |Neil.McCormick@ed.ac.uk |MBChB Assessment Officer |MVM Academic Administration |PC | |

6 Test Schedule Prerequisites

The new version 3.0 of CliniQuest (release by Speedwell end Oct) will have been deployed prior to testing, the new release by Speedwell is due end October. The current version 3.0 of QuestionBank and MultiQuest will also have been deployed prior to the start of user acceptance testing.

8 Test scenarios and Acceptance Level

Current processes are documented below and will form the test scenarios. There should be a test for each of the business processes required.. Acceptance criteria must be identified and detailed.

1. Test 1 – Exam Management using CliniQuest

|Ref |Process |Acceptance Criteria |

|1.1 |Create new OSCE exam in CliniQuest |New exam created, including stations, items, marking components and |

| | |marks; students are associated with an instance of the exam |

|1.2 |Print exam |Exam is able to be printed on to OSCE marksheets |

|1.3 |Modify exam |Exam is able to be modified |

|1.4 |Create then delete another exam |Exam is shown as deleted on the database |

2. Test 2 – Exam Management in QuestionBank

|Ref |Process |Acceptance Criteria |

|2.1 |Create new OSCE exam in QuestionBank |New exam created, including stations and items |

|2.2 |Modify exam |Exam is able to be modified |

|2.3 |Create then delete another exam |Exam is shown as deleted on the database |

3. Test 3 – Export and Import to QuestionBank

|Ref |Process |Acceptance Criteria |

|3.1 |Export from CliniQuest to QuestionBank |An exam or station created in CliniQuest can be exported to QuestionBank |

|3.2 |Import from QuestionBank to CliniQuest |An exam or station created in QuestionBank can be imported by CliniQuest |

4. Test 1

|Ref |Process |Acceptance Criteria |

|1.1 | | |

|1.2 | | |

| | | |

5. Test 2

|Ref |Process |Acceptance Criteria |

|2.1 | | |

|2.2 | | |

6. Test 4 – Repeat Tests 1 to 3 for a non-Administrator user

|Ref |Process |Acceptance Criteria |

|4.1 |Repeat Processes 1.1 to 3.2 |The respective acceptance criteria for 1.1 to 3.2 |

9 Assumptions

• Integration testing of desktop package of the current v3.0 Speedwell software (QuestionBank and MultiQuest) in TEST has been performed by Neil McCormick and Jennifer Hill (planned for Oct 12).

• The UAT environment will be available and fully configured ahead of the UAT. The Test database will have been populated with current MCQ and OSCE data. Testers’ user ids will have been authorized on the new database.

• Testers will test the functionality of the new version 3.0 of the software on the new hosted IS database. Acceptance criteria for each requirement have been identified.

• Resources identified in this plan are available to conduct the UAT and address issues as they are raised by the test team.

The Project Manager must notify the Project Sponsor if any of these assumptions are not correct before commencing the UAT.

I don’t know where in the document to put this comment so I am squeezing it in here:

Note: This is a “USER” acceptance test document. But more testing than end-users can perform will be necessary before I’d accept it as a service. I think (?) that this will arise in a separate document “SLD” or “SLA”. To be acceptable system needs to assure me that it is accumulating and storing the data reliably enough, and that access to the data is set appropriately in particular, to prevent un-authorised access, and that the database is backed up and the schedule for this is made known to me (and to Neil).

Acceptance Test Log

User testing should be based on the test scenarios and acceptance criteria identified above. Any deviation from these scenarios should be noted here.

1 Test Scenarios –detailed steps

All Test Participants listed in this document will complete the testing script using the proposed template below:

1 Test 1

|Name of Participant: |Neil McCormick |

Task 1: Create exam in CliniQuest as Administrator

1. In CliniQuest, create an exam

2. Create stations in the exam

3. Add questions within the stations

4. Add marking components

5. Add marks to each item

6. Modify some properties of the exam

7. Create another exam and then delete it

8. Print a sheet from the original exam

|Test functional scenarios |Acceptance criteria |Results |

|OSCE creation |Exam can be created |Pass/fail |

|Modification |Modifications are made and recorded in the database |Pass/fail |

|Deletion |Exam can be deleted and this is recorded in the database |Pass/fail |

|Printing |Exam sheets can be viewed in print mode and sent to printer |Pass/fail |

2 Test 2

|Name of Participant: |Neil McCormick |

Task 1: Create exam in QuestionBank as Administrator

1. In QuestionBank, create an OSCE exam

2. Create stations in the exam

3. Add questions within the stations

4. Add marking components

5. Add marks to each item

6. Modify some properties of the exam

7. Create another exam and then delete it

|Test functional scenarios |Acceptance criteria |Results |

|OSCE creation |Exam can be created |Pass/fail |

|Modification |Modifications are made and recorded in the database |Pass/fail |

|Deletion |Exam can be deleted and this is recorded in the database |Pass/fail |

3 Test 3

|Name of Participant: |Neil McCormick |

Task 1: Export and import an exam to the QuestionBank

1. Export the exam created in CliniQuest to QuestionBank

2. Import the exam created in QuestionBank into CliniQuest

|Test functional scenarios |Acceptance criteria |Results |

|Export and Import |Files can be exported and imported from and to both CliniQuest and QuestionBank |Pass/fail |

4 Test 4

|Name of Participant: |Judith Bryce |

Task 1: Repeat Tests 1 to 3 on a different PC using a Speedwell user account other than the Administrator account

|Test functional scenarios |Acceptance criteria |Results |

|OSCE creation in CliniQuest |Exam can be created |Pass/fail |

|Modification in CliniQuest |Modifications are made and recorded in the database |Pass/fail |

|Deletion in CliniQuest |Exam can be deleted and this is recorded in the database |Pass/fail |

|Printing from CliniQuest |Exam sheets can be viewed in print mode and sent to printer |Pass/fail |

|OSCE creation in QuestionBank |Exam can be created |Pass/fail |

|Modification in QuestionBank |Modifications are made and recorded in the database |Pass/fail |

|Deletion in QuestionBank |Exam can be deleted and this is recorded in the database |Pass/fail |

|Export and Import |Files can be exported and imported from and to both CliniQuest and |Pass/fail |

| |QuestionBank | |

5 Test 1

|Name of Participant: | |

Task 1: xxx

9. Step1

10. Step2

11. Step3

|Test functional scenarios |Acceptance criteria |Results |

|Description |To pass… |Pass/fail |

Task 2: xxx

|Test functional scenarios |Acceptance criteria |Results |

|Description |To pass… |Pass/fail |

6 Test 2

|Name of Participant: | |

Task 1: xxx

1. Step1

2. Step2

3. Step3

|Test functional scenarios |Acceptance criteria |Results |

|description |To pass… |Pass/fail |

7 Final comment

Please add any additional or overall comments you may have in to this comment box below.

|Additional or Overall Comments: |

| |

|Signature of Participant: | |

Acceptance Test Results

1 Comments and feedback from UAT

2 Issues raised at UAT and follow up

Issues raised at UAT and changed/fixed:

|Issues |Solution |

| | |

| | |

| | |

Replies from UAT re-testers:

3 Open Issues

Any issues identified during UAT must be added to the Test Log. It may be agreed that UAT can be signed off while some issues remain open. 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.

4 Document Sign Off

|Project Manager |Franck Bergeret |date |

|Business Lead |Neil McCormick | |

|Business Assurance Coordinator |David Williamson/Neil McCormick | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download