Other test work products
Beyond test cases and summary reports, testing produces test data, environment specifications, traceability matrices, scripts, logs and incident reports. We create and keep them, so your testing can be repeated, audited and improved.
What we hand over
- TraceabilityRequirements to tests to defects
- Test dataInputs you can reuse
- LogsWhat ran, when, with what result
- ReportsDefects, incidents, summaries
What are test work products?
Test work products are all the artifacts produced during testing that support test execution and give evidence of quality. Beyond test cases and summary reports, they include test data, environment specifications, traceability matrices, test scripts, test logs, incident reports and execution records.
Together they make testing reproducible and provide the audit trail that compliance and continuous improvement depend on.
Core test artifacts
| Artifact | Description | Purpose |
|---|---|---|
| Test data | Structured inputs for test execution, including boundary values, edge cases, invalid inputs and production-like samples. | Execution |
| Test environment specs | The hardware, software, network and infrastructure a test environment needs. | Setup |
| Traceability matrix | A two-way map between requirements, test cases and defects that shows coverage across the test lifecycle. | Coverage |
| Test scripts | Automated test code and manual step-by-step procedures that make a test case repeatable. | Automation |
| Test summary reports | Test results, pass and fail counts, defect statistics and an overall quality assessment for stakeholders. | Reporting |
| Defect reports | Each issue with steps to reproduce, severity, priority, environment and evidence such as screenshots. | Tracking |
| Test logs | A time-ordered record of what was executed, the result, who ran it and under which conditions. | Audit trail |
| Incident reports | Unexpected events during testing, such as environment failures or tool crashes, that need investigating. | Escalation |
Artifact creation workflow
Preparation phase
Define test data requirements, write the environment specifications and build the traceability matrix from requirements to test cases.
Script development
Write automated scripts and manual procedures, with setup steps, prerequisites and the expected order of execution.
Execution logging
Log every run with timestamps, results, environment state and any deviation from the plan.
Issue documentation
Write defect reports for failed tests and incident reports for unexpected events, with everything needed to reproduce them.
Summary reporting
Pull the results into a test summary report with quality metrics and recommendations for stakeholders.
Artifact benefits
Traceability and coverage
Linking requirements to tests and results shows what is covered and what is not.
This gives you: a two-way traceability matrix, requirements coverage, gap analysis, impact analysis for changes.
Reproducibility
Documented data, scripts and environments let another team run the same test months later and get a comparable result.
This gives you: standard test procedures, version-controlled test data, environment configuration templates, automated script execution.
Audit compliance
Logs and reports give auditors and regulators the trail they ask for.
This gives you: a complete execution history, timestamped activity logs, defect lifecycle tracking, compliance documentation.
Continuous improvement
Past artifacts show defect trends and which tests actually find problems.
This shows you: defect density, test execution efficiency, coverage trends and process bottlenecks.
Standard reference
Definitions and practice follow the ISTQB CTFL v4.0.1 syllabus (version 4.0.1). The structure of test documentation is set out in ISO/IEC/IEEE 29119-3, which replaced IEEE 829.
How we plan and report: test plan and defect management.
How BetterQA does test documentation
We produce the work products your project actually needs, in your tracker or in BugBoard, and keep them current as the product changes.
Engineers who test for a living
BetterQA, founded 2018, 50+ QA engineers. People write and maintain the test documentation and explain what it says about your release.
Bugs you can act on
Every defect we find is written up in BugBoard, our own test management tool, or in your tracker, with steps to reproduce, the expected and actual result, and the environment.
A certified process
ISO 9001 for quality management and ISO 27001:2022 for information security. See our certifications.
How an engagement works
- €20-45 per hour
- First month is a trial
- First two weeks complimentary if you are not happy
- 30 days' notice after that
Test work products: common questions
What are test work products?
Everything testing produces besides the tests themselves: test data, environment specifications, traceability matrices, scripts, logs, defect and incident reports, and summary reports.
What is a traceability matrix?
A table that links each requirement to the tests that cover it and the defects found against it, so gaps in coverage are visible.
What is the difference between a defect report and an incident report?
A defect report describes a problem in the product. An incident report records any unexpected event during testing, which may turn out to be a defect, an environment failure or a test mistake.
Which standard covers test documentation?
ISO/IEC/IEEE 29119-3, which replaced IEEE 829. The ISTQB Foundation Level syllabus uses the same terms.
Why keep test logs?
They show what was tested, when and with what result. That is what auditors ask for and what lets you compare one release with the next.
What does it cost?
The cost depends on which work products you need and how often they are updated. Our rate is €20-45 per hour. For ongoing work the first month is a trial, the first two weeks are complimentary if you are not happy, and after that it is 30 days' notice.
Need complete test documentation?
Tell us what your auditors or stakeholders ask for. We will set up the work products that answer them and keep them current every release.