Software Testing Report: Objectives, Execution, Results and Coverage, Summaries of Project Management

A test report template for software projects, detailing testing objectives, execution details, results, and coverage. It includes testing types such as regression, performance, load, and unit tests, with examples of objectives and test suites. The report also covers test execution results, including passed, failed, and skipped tests, as well as defect descriptions.

Typology: Summaries

2021/2022

Uploaded on 07/05/2022

carol_78
carol_78 🇦🇺

4.8

(59)

1K documents

1 / 1

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Test Report Template
Project Information
Project or Release Name/Number
Team assigned (if relevant add team members and roles)
Test Objectives
Testing Executed:
o Regression
Feature/Function
Integration
o Performance & Load
o Unit tests - or any developer side test execution
List out the objective of each type of test. For example, Regression testing for a new feature.
Your objective for Unit Tests may be to ensure each code checkin passes the Unit test suite
indicating the main functions are working as expected.
Test Execution Details
Name of Tests or Test Suites
Location of tests, test suites
Test Execution Results
Number of tests by type
Passed
Failed
Skipped
User or team who executed tests, on what server and what date(s)
Defect number and description for all defects entered from the test effort.
Test Coverage
Graphical illustration of lines of code tested, compared to lines of code in application.
Information that gives the reader a better idea of what is covered by testing.
Test Summary
Paragraph summary of tests executed, results, and defects entered. Reads like a
technical extract - gives you the basic information without the explicit details.

Partial preview of the text

Download Software Testing Report: Objectives, Execution, Results and Coverage and more Summaries Project Management in PDF only on Docsity!

Test Report Template

Project Information

  • Project or Release Name/Number
  • Team assigned (if relevant add team members and roles)

Test Objectives

  • Testing Executed: o Regression ▪ Feature/Function ▪ Integration o Performance & Load o Unit tests - or any developer side test execution List out the objective of each type of test. For example, Regression testing for a new feature. Your objective for Unit Tests may be to ensure each code checkin passes the Unit test suite indicating the main functions are working as expected.

Test Execution Details

● Name of Tests or Test Suites ● Location of tests, test suites

Test Execution Results

  • Number of tests by type
  • Passed
  • Failed
  • Skipped
  • User or team who executed tests, on what server and what date(s)
  • Defect number and description for all defects entered from the test effort.

Test Coverage

● Graphical illustration of lines of code tested, compared to lines of code in application. Information that gives the reader a better idea of what is covered by testing.

Test Summary

● Paragraph summary of tests executed, results, and defects entered. Reads like a technical extract - gives you the basic information without the explicit details.