Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan This material Comp8 _Unit10 was developed by Duke University,

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Test process essentials Riitta Viitamäki,
System Development Life Cycle (SDLC)
 Acceptance testing is a user-run test that demonstrates the application’s ability to meet the original business objectives and system requirements and.
Software Quality Assurance Plan
Designing and Developing Decision Support Systems Chapter 4.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Component 4: Introduction to Information and Computer Science Unit 9: Components and Development of Large Scale Systems Lecture 5 This material was developed.
(c) 2007 Mauro Pezzè & Michal Young Ch 24, slide 1 Documenting Analysis and Test.
1 SOFTWARE LIFE-CYCLES Elements and Definitions. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
Implementation/Acceptance Testing / 1 Implementation and Acceptance Testing Physical Implementation Criteria: 1. Data availability 2. Data reliability.
Testing - an Overview September 10, What is it, Why do it? Testing is a set of activities aimed at validating that an attribute or capability.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Senior Design – Acceptance Test Plan Review The goal is to: define the criteria for approving the application. Tightly coupled to the Requirements document.
Design, Implementation and Maintenance
Software Life Cycle Model
This chapter is extracted from Sommerville’s slides. Text book chapter
Unit 16 Procedural Programming
S/W Project Management
How To Apply Quality Management
Extreme Programming Software Development Written by Sanjay Kumar.
Chapter 8: Systems analysis and design
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Explore.
RUP Implementation and Testing
Module CC3002 Post Implementation Issues Lecture for Week 1 AY 2013 Spring.
Independent User Acceptance Test Process (IUAT)
Introduction to Information and Computer Science Information Systems Lecture c This material (Comp4_Unit9c) was developed by OHSU, funded by the Department.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Installation and Maintenance of Health IT Systems
Comp 14 - Special Topics in Vendor- Specific Systems Unit 8 - Vendor-Specific Go- Live Strategies This material was developed by Columbia University, funded.
Common Activities Activities and Tasks in the WBS.
Unit 8a Troubleshooting; Maintenance and Upgrades; Interaction with Vendors, Developers, and Users Component 8 Installation and Maintenance of Health IT.
Unit 6b System Security Procedures and Standards Component 8 Installation and Maintenance of Health IT Systems This material was developed by Duke University,
Unit 8b Troubleshooting; Maintenance and Upgrades; Interaction with Vendors, Developers, and Users Component 8 Installation and Maintenance of Health IT.
SacProNet An Overview of Project Management Techniques.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Component 8 Installation and Maintenance of Health IT Systems Unit 5 The Software Development Life Cycle This material was developed by Duke University,
Special Topics in Vendor- Specific Systems EHR Go-Live Strategies This material (Comp14_Unit8) was developed by Columbia University, funded by the Department.
The Systems Life Cycle AS Computing F451 AS Computing F451.
Component 8 Installation and Maintenance of Health IT Systems Unit 4 Structured Systems Analysis and Design This material was developed by Duke University,
Risk Management How To Develop a Risk Response Plan alphaPM Inc.
The Software Development Process
Software Testing Process By: M. Muzaffar Hameed.
Component 8 Installation and Maintenance of Health IT Systems Unit 10 Developing a Test Strategy and Test Plan This material was developed by Duke University,
This material was developed by Oregon Health & Science University, funded by the Department of Health and Human Services, Office of the National Coordinator.
Software Engineering Lecture # 1.
Intermediate 2 Computing Unit 2 - Software Development.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Installation and Maintenance of Health IT Systems Unit 8b Troubleshooting; Maintenance and Upgrades; and Interaction with Vendors, Developers, and Users.
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
Unit 17: SDLC. Systems Development Life Cycle Five Major Phases Plus Documentation throughout Plus Evaluation…
1 Systems Implementation Introduction  The chapter will address the following questions:  What is the systems implementation process in terms of the.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Unit 8a: The Implementation Team HIT Implementation Planning for Quality and Safety This material was developed by Johns Hopkins University, funded by.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
UNIVERSITY OF DAR ES SALAAM t Selection and Employment of Consultants Negotiations with Consultants; Monitoring Performance of Consultants; Resolving Disputes.
Installation and Maintenance of Health IT Systems Unit 8a Troubleshooting; Maintenance and Upgrades; and Interaction with Vendors, Developers, and Users.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Introduction to Project Management Project Closure and Transition Lecture a This material (Comp19_Unit11a) was developed by Johns Hopkins University, funded.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
1 DEPLOYMENT AND OPERATIONS MODULE 23 ECM SPECIALIST COURSE 1 Copyright AIIM.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
CONTRACT ADMINISTRATION
Use Cases Discuss the what and how of use cases: Basics Benefits
Description of Revision
Engineering Processes
“Would I have to do this all by myself …….?”
IS&T Project Reviews September 9, 2004.
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan This material Comp8 _Unit10 was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number IU24OC

Developing a Test Strategy and Test Plan Learning Objectives 2 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan 1.Gather user feedback and performance baseline for system validation and testing 2.Document problems with their resolution status 3.Create, execute, and document a test plan (What is Acceptance Testing, n.d.; Tucker, 2003; Wikipedia, 2011)

3 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan What is User Acceptance Testing (UAT)? Usually performed as final step before rollout. Ensures product meets client’s expectations Ensures software meets project objectives Provides opportunity for further debugging Based on mutually agreed-upon deliverables ( Tucker, 2003; Turbit, 2006; What is Acceptance Testing, n.d. )

4 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan When to Test? Prior to rollout Always needed for critical software such as EHR systems Focused on functionality, not technical issues. Most technical and integration bugs should have been worked out prior to testing. ( Tucker, 2003; Turbit, 2006; WikiPedia 2011)

5 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan What are the Testing Steps? 1.Planning the UAT 2.Designing your test cases 3.Creating the UAT team 4.Executing test cases 5.Documenting defects 6.Resolving and debugging 7.Signing off (Kumar, 2007)

What are the Testing Steps? 6 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan TermDescription Test Strategy Staffing and Users, evaluation tools, procedures, and support Test Scenarios What events will be tested Test ScriptsActual, step-by-step inputs that will be used, along with expected results 10.1 Testing Steps (Turbit, 2006)

7 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Test Scenarios vs. Test Scripts Test scenarios –Broad interpretation of what you are testing –Example: “When you enter a prescription that could cause an adverse reaction for the patient, a warning message should appear.” Test Scripts –Step-by-step details of running the tests –Example: “1. Select John Doe’s patient record. 2. Select ‘New Rx’. …”)

8 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan UAT Planning Stage Most important stage in the process Testing strategy developed Key focus areas defined –Based on expected overall product deliverables Entry and exit criteria defined (Kumar, 2007)

9 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Testing Strategy Template A typical testing strategy addresses several categories: –Overview –Testing environment –Procedures –Software The following slides show typical elements in a testing strategy. Your strategy may include more or fewer variables.

Testing Strategy Template: Overview 10.2 Overview of Testing Strategy Template (Turbit, 2006) 10 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan CategoryInstructions Testing stageDefine the type of testing to be done ScheduleEnter testing date(s) LocationWhere testing takes place ParticipantsWho is involved with the testing

Testing Strategy Template: Testing Environment CategoryInstructions IT environment Explain, in detail, the environment used for testing; e.g. number of systems and their use, logins Equipment needed Details of equipment required for testing and setup requirements Data Data required for testing; e.g. 100 fictitious patient records will be accessed, spanning visit dates from Backup requirements How often data should be backed up and who is responsible; also how long backups should be retained Restores Define the circumstances a restore, or data refresh, should take place, along with authorization process 10.3 Testing Environment (Turbit, 2006) 11 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan

Testing Strategy Template: Procedures CategoryInstructions Problem identification Step-by-step procedure to be used when a tester finds a suspected defect. Identify resource(s) to receive all defects; in some cases, there may be more than one resource, e.g. different people for applications problems and operational problems. Defect rectification Step-by-step procedure for how defects will be managed once received. This procedure would normally be under the control of the person or people rectifying the defect. Defect retestingStep-by-step procedure for re-testing rectified defect. 12 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan 10.4 Procedures (Turbit, 2006)

Testing Strategy Template: Procedures (cont’d) 10.5 Procedures (continued) (Turbit, 2006) 13 Health IT Workforce Curriculum Version 3.0/Spring 2012 (Insert Component Title Here) (Insert Unit Title Here) Lecture a CategoryInstructions Sign-off for activities Your test plan should define how each testing activity will be signed off; including all initial testing and any re-testing needed mitigate defects that have been identified. Sign-off for project How total testing will be signed off, including defect rectification process.

Testing Strategy Template: Software CategoryInstructions Test management and performance management software List any specialized test management software and manner of use Testing software Outline any software that will be used during the testing process 10.6 Software (Turbit, 2006) 14 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan

15 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Designing Test Cases Used to test focus areas defined during planning process Often defined during software requirements phase Others created by business analysts or subject matter experts

16 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Testing Scenarios Broadly define scope of each test, with expected output Used to develop detailed scripts needed for end user testing Best generated by experienced testers and subject matter experts (Tucker, 2003; Turbit, 2006)

Creating Test Scenarios: Example 10.7 Data Input and Modification Validation Test (Kumar 2007; Turbit, 2006) 17 Health IT Workforce Curriculum Version 3.0/Spring 2012 (Insert Component Title Here) (Insert Unit Title Here) Lecture a Test No. Input FieldInput TypeInput Anticipated Result Notes I101User NameAlphanumeric Incorrect username Error message I102 Correct username Prompt for Password I102None Error message Password cannot be blank

18 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Test Scripts Include: –Step-by-step instructions for end-user tester –Sections for recording actual output from tests –Instructions for passing along findings to appropriate team members for resolution Last stage before end user tester selection and testing begin (Turbit, 2006)

19 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan End User Testing Team Actual testing team should represent a cross-section of the end user environment. Testing environment should closely mimic the real production environment. (Turbit, 2006; Wikipedia)

20 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Test Scripts Test scripts can vary but usually include: –A column indicating the set number in the process –A column in the test script for the step by step instructions to perform –A column indicating the expected test result –A column for the tester to input the ACTUAL result –A comments field Sometimes, test scripts can be coded and automated using a tool called an interpreter to mimic the user. (Kumar 2007; Turbit, 2006)

21 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Executing the Tests End users execute each of the test scripts, carefully documenting their findings. Also allow testers “free range” on the system to perform relevant random testing to explore for errors. Ensure all documentation is complete and forwarded quickly to proper team members for issue resolution. (Turbit, 2006)

22 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Issue Resolution Issues discovered are discussed with the testing and project team &/or vendor. Development team &/or vendor devises satisfactory solution End user team retests. (Kumar, 2007; Turbit, 2006)

23 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Sign-Off Acknowledgement that UAT team accepts the application All known issues have been satisfactorily resolved. Often represents pay-off point for vendor (Kumar, 2007; Turbit, 2006)

24 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Summary Using talented resources to develop relevant test scenarios is critical to proper system validation and successful testing. Once test scenarios have been conceived, devise test scripts for each scenario. End users or automated programs perform the detailed step-by step testing and record the results.

25 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan Summary (cont’d) Careful documentation and detailed defect resolution plans ensure kinks are worked out and retested. Issues are brought to the test team’s attention to be forwarded to the programmers or vendor for resolution Testing continues until all parties are confident in the software’s performance. Once testing is complete, the client “takes delivery” and can begin implementing its “roll out” strategy

26 Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan References: “Acceptance testing” (2011).Wikipedia.[Internet] Kumar, K. (2007, May 18). Beginners Guide To Software Testing. Retrieved February 10, 2012, from KR Testing Solutions website: Tucker, J. (2003, September). Definition - smoke testing. Retrieved February 10, 2012, from SearchWinDevelopment website: Turbit, N. (2006, January 30). Developing a Test Strategy. Retrieved from PROJECT PERFECT website: What is Acceptance Testing. (n.d.). Retrieved February 10, 2012, from wiseGEEK - Conjecture Corporation website: Developing a Test Strategy and Test Plan References

Charts, Tables, Figures 10.1 Table. Turbit, N. (2006, January 30). Developing a Test Strategy. Retrieved from PROJECT PERFECT website: Table. Turbit, N. (2006, January 30). Developing a Test Strategy. Retrieved from PROJECT PERFECT website: Table., N. (2006, January 30). Developing a Test Strategy. Retrieved from PROJECT PERFECT website: Table. Turbit, N. (2006, January 30). Developing a Test Strategy. Retrieved from PROJECT PERFECT website: Table. Turbit, N. (2006, January 30). Developing a Test Strategy. Retrieved from PROJECT PERFECT website: Table. Turbit, N. (2006, January 30). Developing a Test Strategy. Retrieved from PROJECT PERFECT website: Table. Kumar, K. (2007, May 18). Beginners Guide To Software Testing. Retrieved February 10, 2012, from KR Testing Solutions website: andhttp://kuldeepse.wordpress.com/2007/05/18/beginners-guide-to-software-testing-i/ Turbit, N. (2006, January 30). Developing a Test Strategy. Retrieved from PROJECT PERFECT website: Health IT Workforce Curriculum Version 3.0/Spring 2012 Installation and Maintenance of Health IT Systems Developing a Test Strategy and Test Plan