Health Care Project Testing Process

http://www.h2kinfosys.com | USA: 770 777 1269 | UK: (020) 3371 7615

Testing Process

1. INTRODUCTION

The Testing process ensures that selected work products meet their specified requirements. That goal is typically attained through formal testing procedures that entail the development of testing strategy, plans, and cases and the subsequent implementation of actual testing. Defects found in the testing process are reported, logged and distributed to appropriate entities for resolution and retesting.

Metrics are generated throughout the process and are used to track progress, which is reported at various levels to stakeholders as desired. At the end of the process, a report is developed describing the results of the process and providing an acceptance criteria for product viability for release to the next project phase, or whether more work is required to get the product to a release state.

2. PROCESS FLOW DESCRIPTION FOR TESTING

Process flow steps that have separate and distinct UAT components are denoted accordingly. Conversely, a step that does not specifically call out UAT components is completely applicable to both system integration testing and UAT. The following steps describe the Testing process flow in more detail:

1. Select the products to be tested.

Product selection is driven during the test planning process. Product selection is based on requirements and the release schedule that dictates what products must be tested at a particular time in the project schedule. However, testing may occur on a relatively ad-hoc basis for an emergency release.

Although the schedule is the major component of product selection, resource and environment availability are also considered.

Inputs Outputs Procedures Forms/Templates

Unit tested code

For UAT: products that have successfully passed system/integration test

Selected products Entrance Criteria Test Plan

Transition/Acceptance Form

1

http://www.h2kinfosys.com/

2. Determine Integration Sequence

The project schedule determines the integration sequence which is reflected in the Test Plan(s). The Test Plan is created during the test planning phase and refined as required in the test preparation phase as detailed test cases are developed. Test case development is the responsibility of the tester under the direction of the test lead.


Project Schedule

Testing Schedule

Integration/Testing Sequence

(Embedded in Forms/Templates)

Test Plan

Test Cases

3. Develop Testing and Product Integration Environment

Once the product is selected, the testing environment is developed. This can be accomplished by utilizing and/or modifying an existing environment, or if necessary, developing a new environment. If a new environment is required the Test Lead should complete the Environment Application form to request the environment from the Environment Management Team/


Environment requirements

Appropriate environment


Test Plan

4. Establish Testing and Product Integration Procedures, Policies, and Criteria

The Test Plan describes the scope, approach, and deliverables for verification, validation, and product integration. Roles and responsibilities are also described. Defect reporting and management procedures are established.

Test cases are developed using the Test Case Template. This substep requires close coordination with the Requirements Development process area as test coverage of all requirements in the selected product is essential for a complete and comprehensive verification, validation, and product integration. The Requirements Development process area will also support Requirements traceability which documents proper test case coverage.

Based on the integration requirements, procedures are developed to ensure proper and correct integration. Criteria are developed to evaluate if the integration process is meeting the requirements and the integration schedule.

For UAT: Trainers develop and deliver product-specific training to UAT participants. UAT test scripts are developed.

Defect recording, tracking and management procedures are put into place in this step, and project metrics are established

2

The Test plan is developed by the test lead with approval required by Test Management. The test cases are developed by the actual project testers and approved by the test lead


Requirements

For UAT: Training materials

Test cases

For UAT: Test scripts

Requirements Traceability Matrix

Defect Management Plan

Metrics Strategy

Test Plan

Test Cases

5. Peer Review of Procedures and Policies

Procedures and policies that have been developed in the previous steps will undergo the prescribed Peer Review Process developed by the Quality Assurance (QA) process area. This process entails the following substeps:

a. Prepare artifacts for peer review

b. Engage in peer review

c. Assimilate peer review results into the artifacts


Testing artifacts Peer Reviewed artifacts

Peer Review Process Peer Review Forms

6. Confirm Readiness of Product Components for Integration

The various components are examined with regard to their readiness for final and complete integration. This can take the form of a Test Readiness Review. The Test Readiness review is prepared by the Test Lead and is signed off by the Test Lead prior to the testing phase commencing.


Product components

Build Report

Product components verified ready for integration


Test Readiness Review

3

7. Assemble Product Components

After integration readiness is confirmed, the various components are assembled according to the sequence defined in the Test Plan(s).


Product components

Build Report

Product components assembled for integration


Test Plan

8. Test Phase Entrance Criteria Examination

Entrance criteria will be examined to determine if all conditions required for that phase of testing exist prior to imitation of the actual verification and validation process.

If the criteria are not met, failed criteria are addressed and examined iteratively until all are met successfully. Entrance and Exit Criteria are developed by the Test Lead for each project and documented in the test plan.


Testing artifacts and environment

Entrance determination


Test Plan

9. Test Readiness Review

A Test Readiness Review is performed. A test readiness review is a test phase-independent, formalized and documented process wherein all appropriate parties determine a products “readiness to test”. The end result is a Go/No-go decision to begin the testing process. The project Test Lead is responsible for conducting the Test Readiness Review.


Testing components status

Go/No-go decision Test Readiness Review Test Readiness Review Form

Build Report from CM

10. Perform Testing/Evaluate Assembled Product Components

In this step, the actual verification of the product is conducted. Integration testing is conducted to evaluate the integrated product. This activity consists of the following substeps:

4

a. Implement test cases (for UAT: test scripts)

b. Capture, record and implement the test scripts developed in Step 3.

Testers are responsible for executing test cases under the direction of the Test Lead


Test Case

For UAT: Test Scripts

Defects (Embedded in Forms/Templates)

Test Cases

Defect Reports

Test Metrics Report

Test Scripts

11. Analyze Testing Results

This step is ongoing during testing. Verification results (defects) are assigned to the proper resources for corrective actions, retested, and either closed or rerouted back to the appropriate dispositioning entity. Defect metrics are recoded and reported to designated team members and/or stakeholders. Testers and the project Test Lead are responsible for conducting Test Result Analysis and the Test Lead is responsible for reporting Defects and Test Metrics to Test Management and relevant project stakeholders.


Defects Defect management

Metrics

Test Reports


Defect Reports

Test Metrics Report

12. Exit Criteria Examination

After testing is completed and there is a next phase of testing to be implemented, exit criteria will be examined to determine if all conditions have been met for migration to the next testing phase.

If the criteria are not met, failed criteria are addressed and examined iteratively until all are met successfully. The Test Lead is responsible for developing Exit Criteria and documenting them in the Project Test Plan.

5


Testing results Migration decision Testing Phase Entrance and Exit Criteria and Test Phase Summary Report

For UAT: Test Phase Summary Report

Test Phase Summary Report

13. Package and Deliver the Product or Product Component

After successful testing/evaluation, the product is packaged appropriately and delivered to deployment. The Test Lead is responsible for completing the Test Final Report, and submitting the form to Test Management, and relevant stakeholders for approval.


Tested product Packaged product (Embedded in Forms/Templates)

Test Final Report

14. Process Closure

This last step in the Testing process results in a report that documents the Testing process (in synopsis), contains a summary of the results of the process and a high-level description of any risks that remain at verification completion. The Test Lead is responsible for creating the Test Phase Summary Report and the Test Final Report. These reports require the approval of test management.


Testing results

Testing metrics

Reports

Metrics


Test Final Report

6

Education

Health Care Project Testing Process