The test report is the seventh of nine descriptive reports in this series on report writing. We may be tempted to consider test reports analytical in nature because they require an in-depth review of the test results. But the elements and style of the test report are so prescribed, and the standards so strict, that the report itself seems definitely descriptive. We expect test reports to yield observable, verifiable results. Nothing is left to opinion.
Test reports are indispensable to any business. They prove the reliability of the products we habitually use and ingest. The taste of a peanut butter cup never changes and a ball point pen releases ink with the same the color and thickness thanks to test reports. We start our car and walk onto a plane or train only after engineering teams have delivered numerous test reports on them. Construction crews break ground for buildings in areas whose soil was assessed in test reports. We can safely say that efficacious test reports feed, employ, and house us.
A test report requires several elements. Below are 11 of them:
- Purpose – Why was the test necessary? How did it apply to the business or related project?
- Objective – What outcome did the test aim to achieve?
- Testers – Who were the assigned testing staff?
- Scope – What part of the material, equipment, facility, environment, or project did the test cover?
- Standards – By what criteria was the test to be conducted and its results to be measured?
- Metrics – What were the sequential and final passing and failing measures and adjustments?
- Methods – What were the procedures, including contingencies, of the test?
- Inputs – What tools, equipment, materials, specimens, or other inputs did the test require?
- Results – What outcomes did the test produce?
- Judgment – Did the test meet the standards? Did it pass or fail?
- Follow-up – What consequential next steps were necessary?
Other descriptive reports in this series are:
