Conduct System Testing Readiness Review

Purpose:

<?>

Objective:

<?>

Description:

System Testing readiness involves the verification of Test environment setup and if the system builds properly from the CM repository. The system installation is verified by executing steps as given in the System Installation Guide. The Project Manager shall review the readiness of System Testing by verifying whether:
    • Hardware and software resources, as per the IT Standards Bill of Material (IT BoM), are procured and available for installation at the Test environment.
    • All defects and issues identified during the earlier tests have been closed effectively.
    • Approved System Test Plan and System Test Cases baseline are checked into the CM repository.
    • The CM repository has the system baseline that can be used for building and installation.
    • The Testing Tools, if any required, are available and installed successfully.
       
Test environment is a collection of hardware, software and network components that are similar to, or same as, the Target environment that shall be used for conducting the tests. Before conducting the tests, the requirements for the Test environment shall be understood and the Test environment shall be set up. All the tools and resources required to set up the environment shall be procured before setting up the Test environment.

Entrance Criteria:

  • System Test Cases document baseline communicated
  • System Documentation (SD) prepared and delivered
  • Test environment prepared for System Testing as per specifications in STP
  • Build Procedures and Application Installation verified
  • Test data set up successfully
  • System Testing Schedule developed and communicated

Exit Criteria:

  • System Test Results approved by Project Manager when the system meets the System Testing Pass criteria
  • System/Binaries, System Documentation, System Test Cases, System Test Summary Report (STSR) and Requirements Traceability Matrix (RTM) approved as baseline and entered into the CM repository

Process and Procedures:

Tailoring Guidelines:

  • None

Process Verification Record(s):

  • Release Audit Report before System Testing
    • Stored By: Project Manager
  • E-mail Communication records of Testing Readiness Review Report for System Testing
    • Stored By: Project Manager
  • Release Audit Report before Acceptance Testing
    • Stored By: Project Manager
  • E-mail Communication records of Testing Readiness Review Report for Acceptance Testing
    • Stored By: Project Manager
  • Sign-off Records from End-Users for User Acceptance Tests
    • Stored By: Project Manager
  • Sign-off Records from System Deployment Manager for Non-Functional (Acceptance) Tests
    • Stored By: Project Manager
  • Records of agreement on the Outstanding Defects and Change Requests
    • Stored By: Project Manager
  • Approval Records from Business Project Champion for Acceptance of System
    • Stored By: Project Manager

Measure(s):

  • System Testing – Defect Summary
    Contains data for defects found during System Testing classified by Severity, Origin and Aging
    • Maintained By: Project Manager
    • Submitted By: Testing Lead, when outsourcing the Supplier shall update at the end of System Testing
    • Frequency of Submission: Reported at Senior Management Review conducted in Test phase
  • Acceptance Testing – Defect Summary
    Contains data for defects found during Acceptance Testing classified by Severity, Origin and Aging
    • Maintained By: Project Manager
    • Submitted By: Testing Lead, when outsourcing the Supplier shall update at the end of Acceptance Testing
    • Frequency of Submission: Reported at Senior Management Review conducted in Test phase

References:

  • None