Roles and Activities > Developer Role Set > Implementer > Perform Unit Tests
Note: 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:
To execute unit test, the following steps should be followed:
The execution of testing ends or terminates in one of two conditions:
If testing terminates abnormally, continue with Recover from Halted Tests.
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 and execute the testing again. For additional information, see Activity: Analyze Test failure and Recover From Halted Tests.
If the test results indicate the failures are genuinely due to the target-of-test, then the Execute Test Suite Activity is complete and the Activity: Determine Test Results now be performed.
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