Artifact: Testability Element
| A specialized implementation element that realizes the test-specific behavior that the software supports. | |
| Other Relationships: | Part Of Implementation Model Extended By: - Test Stub |
| Role: | Implementer |
| Optionality/Occurrence: | This artifact is used if you are designing and implementing test-specific functionality. |
| Templates and Reports: | |
| Examples: | |
| UML Representation: | Element in the implementation model, stereotyped as <<testability element>>. |
| More Information: | - Guideline: Implementation Element |
| Input to Activities: - Execute Test Suite - Implement Design Elements - Implement Developer Test - Implement Testability Elements | Output from Activities: - Implement Testability Elements |
Purpose
The purpose of the Testability Element is to implement test-specific functionality that facilitates testing, either manual or automated. There are various types of test-specific behavior, two of which are:
- “Stubs” for implementation elements that you need to simulate or have decided not to include completely in a test target.
- Elements that provide specialized interfaces or output.
Timing
Testability Element are created and modified in parallel with creating and modifying corresponding application or system implementation elements
Responsibility
The Implementer is responsible for this artifact. For additional details, see Responsibility in Artifact: Implementation Element.
The Tester role uses the testability elements to implement and execute tests.