Artifact: Test Component

Test Component |
A stereotype of component in the implementation model. |
| UML representation: |
Component in the implementation model, stereotyped as «test
component». |
| Worker:
|
Implementer |
| Optionality: |
This artifact is only
used if you are designing and implementing test specific functionality. |
| Reports: |
See Artifact:
Component. |
| More
information: |
See Guidelines:
Component |
|
|
The purpose of the test component is to implement the test specific functionality to
facilitate or automate tests. There are two main types of test-specific components:
- Test components that are "stubs" for design classes that you need to simulate
or have decided not to include completely in a test target.
- Test components that are drivers, facilitating the automation of test cases.
The integration tester, system tester, and performance tester,
use the test components to execute the test specific functionality in testing.
See Properties in Artifact: Component.
Test classes are created and modified in parallel with creating and modifying
corresponding application or system components
See Responsibility in Artifact: Component.
See Tailoring in Artifact: Component.
|