When and how to write your report
When to create a test summary report
You SHOULD draft a report at the end of a project, but you MAY do so for the end of each testing cycle. Typically, it will be written for any new service, major change or new developments in existing services, releases, procurements, proof of concepts and innovation products1.
Characteristics of a good test summary report
A Test Summary Report SHOULD have the following characteristics: -
| SHORT: | As a rule of thumb, aim for no more than 8 -- 11 pages. |
| CLEAR: | Information should be clear. Read DHCW's writing checklist for tips. |
| PRECISE: | The information, though concise, should not be abstract as this will not help the reader draw clear conclusions from it. |
| CONSISTENT: | While content will differ, each report SHOULD use the same template. |
The remainder of this guide provides rules for drafting a report, using the template.
Practical tips
SDS-TEM-5 replaces the previous Test Summary Report and Test Certificate templates.
The Test Certificate has been retired with this guide's publication, and Test Certificates SHOULD no longer be produced.
-
WIA-SOP-71 Wales Informatics Assurance GROUP (WIAG) Process, section 2 Scope. ↩