user acceptance testing slide show (1.25 mb ppt)
DESCRIPTION
TRANSCRIPT
1
User Acceptance Testing
CMIS Remediation
2
UAT Meeting Agenda Introductions Purpose of Meeting Summary of Changes What is User Acceptance Testing (UAT)? Expectations The Testing Process Tracking Defects Fixing Defects When and Where Demo of New Case Wizard Q and A
3
Introductions
Mike Pryor, Project Manager Linda Spinks, SWR Test Coordinator Deanna Reader, Group Manager Kelvin Grayson, IT Subject Matter Expert,
[email protected] Mary Ellis, IT Test Coordinator,
4
Purpose of Meeting
Explain Software and Website Remediation Project (SWR)
Discuss User Acceptance Testing Demo of CMIS New Case Wizard Answer Questions
5
Summary of Changes
What is Remediation? What is not included in the project Summary of CMIS Remediation Changes you will see
6
What is UAT?
User Acceptance Testing is a process where the actual users of the system test the remediated functionality to make sure there are no errors or defects.
The users will “Accept” the system when all testing has passed.
7
Expectations
Expectations of IT staffProvide test environment (location,
equipment, software, etc.).Provide instructions and test documentation.Be available to answer questions and address
issues.
8
Expectations (cont.)
Expectations of testersBe available during the scheduled test time,
with minimal interruptions or distractions.Follow instructions carefully.Document any defects or errors, and
communicate to the IT Test Coordinator (Mary) and IT Subject Matter Expert (Kelvin).
Complete UAT within allocated timeframe.
9
The Testing Process
You will be set up with access to the test database.
You will be provided with testing instructions. When you have finished your testing, send your
results via email to Mary and Kelvin.
10
The Testing Process (cont.)
All UAT testers are encouraged to exercise the CMIS application as much as possible to ensure all your work functions are tested. Some of the UAT testers will receive specific test
case documents to run. If you receive a test case document, record in
that document whether the test passed or failed, add comments, then email it to Mary and Kelvin.
11
Test Case Document Example
12
Tracking Defects A “defect” is an error or any situation where the system
does not perform as expected. If a defect is found: Do a print screen if possible. Attempt to duplicate the error. Report the error via email to both Mary and Kelvin. Include detailed information in the email, including
steps to recreate the error, and attach the print screen.
13
Fixing Defects
After a defect is reported,
1. We will investigate and resolve the problem
2. We will let you know when it is resolved
3. You will retest (if necessary) The process will continue until all identified
defects have been resolved, and all test steps in the test cases have passed.
14
When and Where
Dates: Regional staff testing:
• Mon, July 7 thru Wed, July 9• Retesting July 10 and 11
Central Office staff testing: • Mon, July 13 thru Wed, July 15• Retesting July 16 and 17
Time: 9:00-3:00 each day. Duration: 30 minutes to one hour Place: You will work from your own workstation.
15
Demo
Demo of the CMIS New Case Wizard
16
Q and A
Any questions?
17
Login
18
Home Page
19
Search by Case Number
20
Search by Client Info
21
Search by Tracking Number
22
Client
23
Guardian
24
Financial
25
Insurance
26
Medical/General
27
Medical/Diagnosis
28
Medical/Doctor
29
Logout