15 Software Testing Reports

Test Reports in Software Testing

• There are standard and non-standard reports in software testing.
• Standard reports are created as part of the testing life cycle, including:
  • Test Progress Report (TPR): Created multiple times at different milestones, providing a summary of testing performed during a specific period.
  • Test Summary Report: Created once at the end of the project or release, summarizing the entire testing process.

Test Progress Report (TPR)

• Created at multiple milestones throughout the lifecycle.
• Includes information on:
  • Summary of testing performed.
  • Information on what occurred during the test period.
  • Status of testing at that point in time.
  • Deviations from the plan.
  • Critical defects found.
  • Metrics on defects, execution statistics, and resource consumption.
  • Risk mitigation and residual risk status.
  • Reusable test work products produced during that cycle.

Test Summary Report

• Created once at the end of the project or release.
• Includes the same information as the TPR but covers the entire project or release.

Non-Standard Reports

• Daily reports: Individual testers may be required to submit daily reports on their work.
• Defect reports: Establishing traceability between each item, including defects and their status.
• Test logs: Record of test executions, including passed and failed tests.
• Ad-hoc reports: May be requested by stakeholders, such as test coverage or requirement coverage.

Standard Reports

• Standard reports are created as part of the testing life cycle
• Two types of standard reports: Test Progress Report (TPR) and Test Summary Report

Test Progress Report (TPR)

• Created multiple times at different milestones
• Provides a summary of testing performed during a specific period
• Includes information on:
  • Summary of testing performed
  • Information on what occurred during the test period
  • Status of testing at that point in time
  • Deviations from the plan
  • Critical defects found
  • Metrics on defects, execution statistics, and resource consumption
  • Risk mitigation and residual risk status
  • Reusable test work products produced during that cycle

Test Summary Report

• Created once at the end of the project or release
• Summarizes the entire testing process
• Includes the same information as the TPR but covers the entire project or release

Non-Standard Reports

• Types of non-standard reports:
  • Daily reports: Individual testers submit daily reports on their work
  • Defect reports: Establishing traceability between each item, including defects and their status
  • Test logs: Record of test executions, including passed and failed tests
  • Ad-hoc reports: May be requested by stakeholders, such as test coverage or requirement coverage

Learn about standard and non-standard reports in software testing, including Test Progress Reports and Test Summary Reports. Understand their purpose and creation milestones.