Artifact:  Test Subsystem

Test Subsystem	A kind of implementation subsystem, in the implementation model, containing test-related components.
UML representation:	Package in the implementation model, stereotyped as «test subsystem».
Role:	Implementer
Optionality:	This artifact is only used if you are designing and implementing test specific functionality.
More information:	Guideline: Implementation Subsystem
Purpose Properties Timing Responsibility Tailoring

Input to Activities: Execute Test

Output from Activities: Implement Test Components and Subsystems

Purpose

The purpose of the test subsystem is to implement the test specific functionality to facilitate or automate tests. There are two main types of test-specific subsystems:

• Test subsystems that are "stubs" for design classes that you need to simulate or have decided not to include completely in a test target.
• Test subsystems that are drivers, facilitating the automation of test cases.

The Tester uses the test subsystems to execute the test specific functionality in testing. The test subsystem is a kind of implementation subsystem.

Properties

See Properties in Artifact: Implementation Subsystem.

Timing

Test subsystems are created and modified in parallel with creating and modifying corresponding application subsystems.

Responsibility

See Responsibility in Artifact: Implementation Subsystem.

Tailoring

See Tailoring in Artifact: Implementation Subsystem.

Copyright  © 1987 - 2001 Rational Software Corporation

Rational Unified Process