Test Work Product

Definition

Test Work Product: a work productthat may be produced during the testing activity
Test Set: the cohesive set of all test work products

The following testing documents may be produced during the testing activity:

Project Test Plan,
which formally documents the plans for performing all testing on an endeavor.
Master Test List,
which lists all system and launch test suites of test cases on an endeavor.
Test Procedure,
which formally documents how to manually execute a test suite of test cases.
Test Report,
which formally reports the results of the execution of a test suite of test cases.
Test Summary Report,
which formally summarizes the results of all testing on an endeavor.
Usability Test Screening Questionnaire,
which is an organized list of questions that is used to select and understand test participants for system usability testing.
Usability Test Orientation Script,
which formally documents standard pretest information to be read verbatim to each test participant.
Usability Test Observations Form,
which is a form that is used to expedite the collection of relevant test data by the test monitor.
Usability Pretest Questionnaire,
which is an organized list of questions that are answered by the test participants and that are used to address specific test objectives prior to system usability testing.
Usability Posttest Questionnaire,
which is an organized list of questions that is used to obtain the test participants’ observations, opinions, preferences, and recommendations concerning the work product under test.

The following testing software and data may be produced during the testing activity:

Test Harness,
which is a software tool that automates the testing process by running test suites of test cases.
Test Script,
which is a software program (often written in a procedural scripting language) that executes a test suite of test cases.
Test Suite,
which is a cohesive collection of related test cases.
Test Case,
which is the test software that automatically performs a single test on an executable work product.
Test Data,
which is the cohesive information (e.g., data, content, or objects) that exists in the form of a file or database that tests need to execute successfully.

Different endeavors require different processes, which in turn will require different testing work products.
Every endeavor does not require the production of every testing work product.
Select only those testing work products that are appropriate for the endeavor.
Selected testing work products should be:
- Relevant.
- Useful.
- Usable.
- Cost-effective.