WORKERS AND ARTIFACTS

Two main workers are involved in the test workflow:

The Test Designer is responsible for the planning, design, implementation, and evaluation of testing. This involves generating the test plan and test model, implementing the test procedures, and evaluating test coverage, results, and effectiveness.
The Tester is responsible for executing the system tests. This effort includes setting up and executing tests, evaluating test execution, recovering from errors, assessing the results of testing, and logging change requests .

When specific code (such as drivers or stubs) must be developed to support testing, the designer and the implementer are also involved in roles similar to the ones defined in Chapters 10 and 11.

Figure 12-2 shows the workers and artifacts in the test workflow. The key artifacts of testing are as follows :

Figure 12.02. Workers and artifacts in the test workflow

The Test Plan contains information about the purpose and goals of testing in the project. The test plan identifies the strategies to be used and the resources needed to implement and execute testing.
The Test Model was described earlier.
Test Results are the data captured during the execution of tests.
A Workload Model for performance testing identifies the variables and defines their values used in the different performance tests to simulate or emulate the actor characteristics and the end user 's business functions (use cases), their load, and their volume.
Defects generated as a result of failed tests are one kind of change request (see Chapter 13).

In addition to these artifacts, the following artifacts are produced when test-specific code must be developed:

Test packages and classes
Test subsystems and components

A test evaluation summary is used as part of the project iteration assessment and periodic status assessment (see Chapter 7, The Project Management Workflow).