WORKFLOW

WORKFLOW

Figure 12-3 illustrates the typical testing workflow, showing the major workflow details and their dependencies.

Figure 12.03. The test workflow

Plan Test

The purpose is to identify and describe the testing that will be implemented and executed. This is accomplished by generating a test plan that contains the requirements for test and test strategies. A single test plan may be developed, describing all the types of tests to be implemented and executed, or one test plan per type of test may be developed. Either method is acceptable. Test planning is done so the test efforts can be measured and managed.

Design Test

The purpose is to identify, describe, and generate the test model and its reported artifacts. Test design is done to ensure that the test software meets its requirements and is structured and organized well. In the design activity, the test designer analyzes the target-of-test and develops the test model and, in the case of performance test, the workload model. Test design transforms use cases into acceptance and system test cases, and use-case realizations into unit, integration, and system test cases. These test cases then drive the design of the software elements that will implement the tests.

Implement Test

The purpose is to implement the test procedures that were defined in the Design Test section. The creation of test procedures usually is done in the context of a test automation tool or programming environment. The output artifact is a computer-readable version of the test procedure, referred to as a test script.

If special test code (e.g., a test harness, drivers, or stubs) is needed to support or perform testing, the designer and the implementer work with the test designer to design and implement the test code.

Execute Tests in Integration Test Stage

The purpose of the Integration Test Stage is to ensure that, during assembly, the system's components collaborate as intended, as well as that the increment has the right behavior. The system integrator compiles and links the system in increments . For each increment, the functionality that has been added is tested , and regression tests are performed, producing test results.

Within an iteration, integration testing is performed several times until the whole system (as defined by the goal of the iteration) has been integrated successfully.

Execute Tests in System Test Stage

The purpose of the System Test Stage is to ensure that the complete system functions as intended. The system integrator compiles and links the system in increments. Each increment needs to go through testing of the functionality that has been added, as well as all tests the previous builds went through (regression tests), producing test results.

Within an iteration, system testing is performed several times until the whole system (as defined by the goal of the iteration) has functioned as intended and meets the test's success or completion criteria.

Evaluate Test

The purpose of evaluating a test is to deliver and assess the quantifiable measures of testing to determine the quality of the target-of-test and the quality of the test process. This is accomplished by reviewing and evaluating the test results, identifying and logging change requests , and calculating the key measures of test.