 |
This artifact is a specification of an execution flow with a specific set of data that results in a measurable expected outcome. |
|
|
Purpose
The purpose of this artifact is to evaluate the software, system, or element for a particular situation to make sure
that it behaves correctly.
|
Relationships
Contained Artifacts |
|
Roles | Responsible:
| Modified By:
|
Tasks | Input To:
| Output From:
|
Description
Main Description |
A test suite is a collection of test cases for a
particular test. It tests the behavior of the software, system, or element under test in very specific
circumstances. There are three major types of testing:
-
Unit Testing - Detailed tests of classes and their participation in mechanisms.
-
Integration Testing - Testing of large collaborations of classes and mechanisms
as they are integrated into components, subsystems, and systems.
-
Validation Testing - Testing of the entire system to ensure adherence to the
behavioral specifications.
|
Notation | Sequence diagrams, activity diagrams, and state diagrams are often used, with accompanying descriptive text. |
Illustrations
Key Considerations
A test suite must be highly specific in terms of sequence of actions and/or events, data values, and measurable
outcomes. |
Tailoring
Impact of not having | This work product defines the control flow and data set for specific tests. Without this definition, it is impossible to
manage a repeatable set of tests for reliable system testing. |
Representation Options |
Activity diagrams and state machines can be used to specify a test suite.
|
More Information
|