yandex

test summary report & template

Sunday, 25 May 2014 08:14

In this article I’ll discuss the first step for ensuring of transparency between testing department and customer.

It is best to build the relationship in such a way that the customer sees what is happening and what he pays money for. Over time, if our relationship is transparent and we continue working with this person, this relationship is improving. This person begins trusting more and more.

Rule: Quality work + Full transparency of what is happening in the sum gives us confidence of the customer.

Let’s talk directly about the reporting.

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

Why Required?

Summarizes all of the testing that was performed since the previous test summary report.

Enables project management and customer to know the status of project testing.

Project Management and end customer can:

  • Get project testing status
  • Get application quality status
  • Take corrective actions, if required

Guidelines

  1. It should be in metrics, charts and table forms, if possible
  2. To write a test summary report, pre requisites are required – test plan should be completed, test execution should occur and respective test reports should be available.

Content of Test Summary Report

GENERAL INFORMATION

  1. IObjective
  2. Reference document

Test Stage:

  1. Unit Testing
  2. Functionality Testing
  3. Integration Testing
  4. System Testing
  5. Interface Testing
  6. Performance Testing
  7. Regression Testing
  8. Acceptance Testing
  9. Exploratory Testing
  10. Test Case Number
  11. Summary Review Date

TESTING

For each kind of testing summarized, a test summary report will include the following information:

Test Suite Information:

  1. o Number of test suites planned.
  2. o Number and percentage of test suites implemented.
  3. o Number and percentage of test suites executed.

Test Case Information:

  1. o Number of test cases planned.
  2. o Number and percentage of test cases implemented.
  3. o Number and percentage of test cases executed.
  4. o Number and percentage of test cases passed.
  5. o Number and percentage of test cases failed.

TEST SUMMARY

  1. Test Summary
  2. Summary of Results
  3. Evaluation
  4. Corrective Action Plan (CAP)
  5. APPROVALS
IntexSoft logo

IntexSoft 2017. All rights reserved.

IntexSoft is in the Clutch Top 10 of Belarusian Web & Software Developers More