Activity:
|
Purpose
|
|
Role: Implementer | |
Frequency: As required, typically multiple times per iteration, especially in Construction, Transition, and Elaboration phases. | |
Steps | |
Input Artifacts: | Resulting Artifacts: |
Tool Mentors: | |
More Information: |
Workflow Details: |
Purpose | To prepare for implementing the test. |
Implementation and modification of components takes place in the context of configuration management on the project. Implementers are provided with a private development workspace (see Activity: Create Development Workspace) in which they do their work, as directed by Artifact: Work Orders. In this workspace, source elements are created and placed under configuration management, or they are modified through the usual check out, edit, build, unit test, and check in cycle (see Activity: Make Changes). Following the completion of some set of components, as defined by one or more Work Orders and required for an upcoming build, the implementer will deliver (see Activity: Deliver Changes) the associated new and modified components to the subsystem integration workspace, for integration with the work of other implementers. Finally, at a convenient point, the implementer can update, or re-baseline, the private development workspace so it's consistent with the subsystem integration workspace (see Activity: Update Workspace).
Unit means not only a class in an object-oriented language, but also free subprograms, such as functions in C++.
For testing each unit (implemented class), perform the following steps:
Purpose | To execute the test procedures, or test scripts if testing is automated. |
To execute unit test, the following steps should be followed:
Note: Executing the test procedures will vary depending on whether testing is automated or manual, and whether test components are needed as either drivers or stubs.
- Automated testing: The test scripts created during the Implement Test step are executed.
- Manual execution: The structured test procedures developed during the Structure Test Procedure activity are used to manually execute the test.
Purpose | To determine whether the tests completed successfully and as desired. To determine if corrective action is required. |
The execution of testing ends or terminates in one of two conditions:
If testing terminates normally, then continue with the step Verify Test Results.
If testing terminates abnormally, continue with the step Recover from Halted Tests.
Purpose | To determine if the test results are reliable. To identify appropriate corrective action if the test results indicate flaws in the test effort or artifacts. |
When testing is complete, review the test results to ensure the test results are reliable and reported failures, warnings, or unexpected results were not caused by external influences (to the target-of-test), such as improper setup or data.
If the reported failures are due to errors identified in the test artifacts or due to problems with the test environment, take the appropriate corrective action to recover from halted tests and then execute the testing again.
If the test results indicate the failures are genuinely due to the target-of-test, then this activity is essentially complete and typically either the Activity: Submit Change Request or the Activity: Analyze Runtime Behavior should now be performed.
Purpose | To determine the appropriate corrective action to recover from a halted test. To correct the problem, recover, and execute the tests again. |
There are two major types of halted tests:
Both types of abnormal termination to testing may exhibit the same symptoms:
To recover from halted tests, perform these steps:
See Activity: Analyze Test Failure for additional information.
Rational Unified Process |