Introduction

Purpose

A Test Summary Report tells readers whether your software needs corrective action, can proceed to the next stage or is ready for release. So it SHOULD provide a clear summary of the test process, results, and key metrics.

This document instructs you on how to write a Test Summary Report. It is guided by the ISO 29119-3:2013[^1] standard for writing a Test Completion Report, although the headings used in the Test Summary Report template vary.

When you are ready to start, base your report on the SDS-TEM-5 Test Summary Report template.

Scope

In-scope

• This guide SHOULD be followed by anyone asked to submit a Test Summary Report to the Welsh Informatics Assurance Group.

Out-of-scope

• Other reports such as Test Progress and Test Defect reports are out-of-scope.

Roles & responsibilities

A Test Summary Report: -

• SHOULD be written and signed by a Test Analyst or person with equivalent knowledge, skills and experience. If your circumstances differ, please contact the document author.

• MUST be acknowledged as reviewed and signed as approved by a Lead Test Analyst, Test Team Principal or person with equivalent knowledge, skills and experience.

• MUST be signed as approved by at least one of the following: -

• Product Specialist or person acting in that capacity.

• Application or Product Manager.

• A representative of a suitable Assurance Group or Project/Programme Board.

References

Conventions

This section follows the handbook-wide conventions for RFC 2119 key words and callout boxes.

[^1] And later versions.