Test Summary Report

Definition

A test summary report is a testing work product that formally summarizes the results of all testing on an endeavor.

Objectives

The typical objectives of a test summary report are to:

• Summarize all of the testing that was performed since the previous test summary report.
• Enable project management andthe customer to know the status of project testing.

Benefits

The typical benefits of a test summary report include:

• Project management and the customer are informed of the current status of project testing.
• Project management and the customer are informed of the current status of application quality.
• Project management and the customer can take corrective action if necessary.

Contents

The typical contents of a test summary report include:

• Test Summary
  • Unit Testing Summary
  • Integration Testing Summary
  • System Testing Summary
  • Launch Testing Summary
• List of Severity One Failures
• Testing Issues Requiring Resolution
• Appendices:
  • TBDs
  • Assumptions

• Test Suite Information:
  • Number of test suites planned.
  • Number and percentage of test suites implemented.
  • Number and percentage of test suites executed.
• Test Case Information:
• Number of test cases planned.
• Number and percentage of test cases implemented.
• Number and percentage of test cases executed.
• Number and percentage of test cases passed.
• Number and percentage of test cases failed (total and by severity).

Stakeholders

• Producers:
  • The Software Development Team for unit tests and low-level software integration tests.
  • The Integration Team for high-level software integration tests and system integration tests.
  • The Independent Test Team for most system and launch tests.
  • The Security Team for security test.
  • The User Experience Team for usability tests:
• Evaluators:
  • The Test Inspection Team.
• Approvers for system and launch test procedures:
  • Technical Leader
  • Project Manager
  • Customer Representative
• Maintainers:
  • The Integration Team for high-level software integration tests and system integration tests.
  • The Independent Test Team for most system and launch tests.
  • The Security Team for security test.
  • The User Experience Team for usability tests:
• Users:
  • The Project Managment Team uses the test summary reports to perform trend analysis in order to:
    • Estimate when the application will be ready for production.
    • If the application requires minor or major defect removal prior to being placed into production.
    • If the application is ready to be placed into production (including defect related risks).
  • The Process Team uses the test reports to identify potential problems with:
    • The development process so that it can be tailored and the OPF can be improved.
    • Staff training so that additional training and mentoring can be provided.
  • The Customer Representative uses the test summary report to keep track of the status of testing.

Phases

• Business Strategy: Not Applicable
• Business Optimization: Not Applicable
• Initiation: Started
• Construction: Completed
• Delivery: Maintained
• Usage: Maintained
• Retirement: Archived

Preconditions

A test summary report typically can be started if the following preconditions hold:

• The Project Test Plan has been completed.
• Testing has occurred.
• The associated test reports are available.

Inputs

The typical inputs to a test summary report include:

• Work Products:
  • Project Test Plan
• Stakeholders:
  • None

Guidelines

• Test summary reports should be generated on a regular basis.
• The test summary results can be supplied in the form of tables, matricies, or charts.
• Electronic copies of test summary reports should be maintained at least until delivery (and possibly for a period afterwards in order to prove that the system was adequately tested.

Conventions

A test summary report is typically constrained by the following conventions:

• Content and Format Standard
• Template
• Inspection Checklist

Examples

• Example Test Summary Report