Wednesday 25 January 2012

Entry and Exit Criteria of Test Phase

 

1. Sprint Testing Phase

In order to alleviate the problem of late discovery of defects it is expected that the testing of sprints are done on parallel with the development, with in sprints. It is expected that earlier functional testing will be performed against part-developed code so that the developers receive immediate feedback on quality. Developers will communicate to testers when components are at a “Testable” stage.

Entry Criteria

  • Requirement Specification are Developed
  • Story Documents Developed
  • Requirement Specifications Reviewed
  • Story Documents Reviewed
  • Test Strategy Developed
  • Test Plan Developed
  • Test Case Specifications Developed
  • Test Case Specifications Reviewed
  • Traceability Matrix Developed
  • Trunk Build available with Developed Components
  • Unit Test Result available
  • Notification of any architecture changes
  • Test Environment Setup

Inputs are:

  • Test Plan
  • Test Strategy
  • Test Case Specification
  • Testing Traceability Matrix

Exit Criteria

  • All Test Cases executed and saved
  • All bugs recorded in Bug Tracking tool
  • Updated Traceability Matrix
  • All Test Cases are Automated
  • Test Report developed
  • Product help file and product training documentation complete

 

2. Alpha Testing Phase

System (functional) Test coverage will provide full end to end testing of functional aspects of Project scope.

Entry Criteria

  • Requirement Specifications are updated covering all the functionality developed in the project
  • Story Developments are updated covering all the stories completed
  • Upgrade path/Utility available, functional tested
  • Passed Build (Unit Test Passed on the build generated)
  • Passed Installation test
  • Test Case Specifications are updated covering all the functionality developed in the project

Inputs are:

  • Test Plan
  • Test Strategy
  • Test Case Specification
  • Test Traceability Matrix

Exit Criteria

  • All Test Cases executed and saved
  • All bugs recorded in Bug Tracking tool
  • Test Report generated (Weekly & Final)
  • Any Test Case marked as NA or Not Applicable are reviewed and agreed by UAT team and Project Manager
  • Automation Test Script are generated for all the functionality developed in the project
  • 95% of Automated Test Suite passed
  • No outstanding Bugs ‘Major’, ‘Critical’, ‘Blocker’, Any exceptions agreed by Project Manager
  • ‘Major’, ‘Critical’, ‘Blocker’ defects can be deferred only if they have been reviewed and approved by UAT users, Business users and Project Manager
  • No outstanding Priority 1 or 2 bugs. Any exceptions approved by Project Manager
  • All outstanding Bugs logged agreed with Project Manager
  • Approved Beta Release

 

3. Beta Testing Phase

Once Project development is complete and System Tested, Test Team will commence the beta test program against the Beta Release trunk. The testing should retest all the functionality of the product using customer scenarios and in parallel Load, Stress and Performance Testing are conducted.

The trunk will continue to be built daily to include amendments and outstanding code fixes. All amendments will be retested and all fixes verified. Fixes and verification will also include comments and bugs raised by customers testing the Beta Release.

During all Test phases, Weekly Load and Stress Testing of Trunk Build will be performed. Load, Stress and Performance testing result should be approved prior to Project Release.

 

Entry Criteria

  • Fully System Tested Trunk Build
  • Overnight Build and Smoke Pass
  • Installation Test Pass
  • Project Upgrade test Pass
  • Load and Stress Test Benchmarked with no adverse memory increase
  • Code Freeze

 

Exit Criteria

  • Everybody test week completed
  • All Test Cases executed and saved
  • Complete Test Team Beta Test
  • Complete Customer Beta Test
  • Updated Test Traceability Matrix
  • Updated System Test Report
  • No outstanding Bugs ‘Major’, ‘Critical’, ‘Blocker’. Any exceptions agreed by Project Manager
  • No outstanding Priority 1 or 2 bugs. Any exceptions approved by Project Manager
  • All outstanding Bugs logged agreed with Project Manager
  • Approved Performance Test Results
  • Approved Load and Stress Test Result with no adverse memory increase
  • Approved Release

No comments:

Post a Comment