08- Installation and Maintenance of Health IT Systems- Unit 10- Developing a Test Strategy and Test...

8/11/2019 08- Installation and Maintenance of Health IT Systems- Unit 10- Developing a Test Strategy and Test Plan

1/27

Installation and Maintenance of

Health IT SystemsDeveloping a

Test Strategy and Test Plan

This material Comp8 _Unit10 was developed by Duke University, funded by the Department of Health and HumanServices, Office of the National Coordinator for Health Information Technology under Award Number IU24OC000024.


2/27

Developing aTest Strategy and Test Plan

Learning Objectives

2Health IT Workforce CurriculumVersion 3.0/Spring 2012

Installation and Maintenance of Health IT SystemsDeveloping a Test Strategy and Test Plan

1. Gather user feedback and performance baselinefor 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/27



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/27



When to Test?

Prior to rollout Always needed for critical software such

as EHR systems

Focused on functionality, not technicalissues. Most technical and integrationbugs should have been worked out prior to

testing.( Tucker, 2003; Turbit, 2006; WikiPedia 2011)


5/27



What are the Testing Steps?

1. Planning the UAT2. Designing your test cases3. Creating the UAT team

4. Executing test cases5. Documenting defects6. Resolving and debugging

7. Signing off(Kumar, 2007)


6/27

What are the Testing Steps?



Term Description

Test Strategy Staffing and Users, evaluation tools, procedures,and support

Test Scenarios What events will be tested

Test Scripts Actual, step-by-step inputs that will be used, alongwith expected results

10.1 Testing Steps (Turbit, 2006)


7/27



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 thepatient, 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/27



UAT Planning Stage

Most important stage in the process Testing strategy developed Key focus areas defined

Based on expected overall productdeliverables

Entry and exit criteria defined

(Kumar, 2007)


9/27



Testing Strategy Template

A typical testing strategy addresses severalcategories: Overview

Testing environment Procedures Software

The following slides show typical elements in

a testing strategy. Your strategy may include more or fewervariables.


10/27

Testing Strategy Template:Overview

10.2 Overview of Testing Strategy Template (Turbit, 2006)



Category Instructions

Testing stage Define the type of testing to be done

Schedule Enter testing date(s)

Location Where testing takes place

Participants Who is involved with the testing


11/27

Testing Strategy Template:Testing Environment


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

DataData required for testing; e.g. 100 fictitious patientrecords will be accessed, spanning visit dates from2001-2005

Backuprequirements

How often data should be backed up and who isresponsible; 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)




12/27

Testing Strategy Template:Procedures


Problem identification

Step-by-step procedure to be used when a tester findsa suspected defect. Identify resource(s) to receive alldefects; in some cases, there may be more than oneresource, e.g. different people for applicationsproblems and operational problems.

Defect rectification

Step-by-step procedure for how defects will bemanaged once received. This procedure wouldnormally be under the control of the person or peoplerectifying the defect.

Defect retesting Step-by-step procedure for re-testing rectified defect.



10.4 Procedures (Turbit, 2006)


13/27

Testing Strategy Template:Procedures (contd)

10.5 Procedures (continued) (Turbit, 2006)


(Insert Component Title Here)(Insert Unit Title Here)

Lecture a


Sign-off for activities

Your test plan should define how each testing activitywill be signed off; including all initial testing and anyre-testing needed mitigate defects that have beenidentified.

Sign-off for project How total testing will be signed off, including defectrectification process.


14/27

Testing Strategy Template:Software


Test management andperformance managementsoftware

List any specialized test management softwareand manner of use

Testing software Outline any software that will be used during thetesting process

10.6 Software (Turbit, 2006)




15/27



Designing Test Cases

Used to test focus areas defined duringplanning process

Often defined during softwarerequirements phase

Others created by business analysts orsubject matter experts


16/27



Testing Scenarios

Broadly define scope of each test, withexpected output

Used to develop detailed scripts neededfor end user testing

Best generated by experienced testersand subject matter experts

(Tucker, 2003; Turbit, 2006)


17/27

Creating Test Scenarios:Example

10.7 Data Input and Modification Validation Test (Kumar 2007; Turbit, 2006)


(Insert Component Title Here)(Insert Unit Title Here)

Lecture a

TestNo. Input Field Input Type Input

AnticipatedResult Notes

I101 User Name Alphanumeric IncorrectusernameErrormessage

I102 CorrectusernamePrompt forPassword

I102 None Errormessage

Passwordcannot beblank


18/27



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 selectionand testing begin

(Turbit, 2006)


19/27



End User Testing Team

Actual testing team should represent across-section of the end user environment.

Testing environment should closely mimicthe real production environment.

(Turbit, 2006; Wikipedia)


20/27



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 tomimic the user.

(Kumar 2007; Turbit, 2006)


21/27



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 testingto explore for errors. Ensure all documentation is complete and

forwarded quickly to proper teammembers for issue resolution.

(Turbit, 2006)


22/27



Issue Resolution

Issues discovered are discussed with thetesting and project team &/or vendor.

Development team &/or vendor devisessatisfactory solution

End user team retests.

(Kumar, 2007; Turbit, 2006)


23/27



Sign-Off

Acknowledgement that UAT team acceptsthe application

All known issues have been satisfactorilyresolved.

Often represents pay-off point for vendor

(Kumar, 2007; Turbit, 2006)


24/27



Summary

Using talented resources to develop relevanttest scenarios is critical to proper systemvalidation 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/27



Summary (contd)

Careful documentation and detailed defectresolution plans ensure kinks are worked out andretested.

Issues are brought to the test team s attention to beforwarded to the programmers or vendor forresolution

Testing continues until all parties are confident in thesoftware s performance.

Once testing is complete, the client takes deliveryand can begin implementing its roll out strategy


26/27



References: Acceptance testing (2011).Wikipedia.[Internet] http://en.wikipedia.org/wiki/Acceptance_testing . Kumar, K. (2007, May 18). Beginners Guide To Software Testing . Retrieved February 10, 2012, from KR Testing

Solutions website: http://kuldeepse.wordpress.com/2007/05/18/beginners-guide-to-software-testing-i/ Tucker, J. (2003, September). Definition - smoke testing . Retrieved February 10, 2012, from

SearchWinDevelopment website: http://searchwindevelopment.techtarget.com/definition/smoke-testing Turbit, N. (2006, January 30). Developing a Test Strategy . Retrieved from PROJECT PERFECT website:

http://www.projectperfect.com.au/downloads/Info/info_test_strategy.pdf What is Acceptance Testing . (n.d.). Retrieved February 10, 2012, from wiseGEEK - Conjecture Corporation

website: http://www.wisegeek.com/what-is-acceptance-testing.htm .

Developing aTest Strategy and Test Plan

References
http://en.wikipedia.org/wiki/Acceptance_testinghttp://searchwindevelopment.techtarget.com/definition/smoke-testinghttp://www.projectperfect.com.au/downloads/Info/info_test_strategy.pdfhttp://www.wisegeek.com/what-is-acceptance-testing.htmhttp://www.wisegeek.com/what-is-acceptance-testing.htmhttp://www.wisegeek.com/what-is-acceptance-testing.htmhttp://www.wisegeek.com/what-is-acceptance-testing.htmhttp://www.wisegeek.com/what-is-acceptance-testing.htmhttp://www.wisegeek.com/what-is-acceptance-testing.htmhttp://www.wisegeek.com/what-is-acceptance-testing.htmhttp://www.wisegeek.com/what-is-acceptance-testing.htmhttp://www.projectperfect.com.au/downloads/Info/info_test_strategy.pdfhttp://searchwindevelopment.techtarget.com/definition/smoke-testinghttp://searchwindevelopment.techtarget.com/definition/smoke-testinghttp://searchwindevelopment.techtarget.com/definition/smoke-testinghttp://en.wikipedia.org/wiki/Acceptance_testing


27/27

Date post:	03-Jun-2018
Category:	Documents
Upload:	health-it-workforce-curriculum-2012
View:	215 times
Download:	0 times

08- Installation and Maintenance of Health IT Systems- Unit 10- Developing a Test Strategy and Test...

Documents