Test Plans - Reference
- Support Advocate (ease solutions)
- Angelica Salazar
- David Sedlock
Overview
A test plan consists of related test cases that are combined into a unit that is convenient to execute. The attributes of test plans and the views in which they are managed are explained below.
Test Plan Attributes
Plan Name | The name identifies the test plan, which is set during creation of the test plan, but can be changed at any time. The names of test plans must be unique within a project. The name is used to select a test plan in the execution view. |
Description | An optional description to document the test plan. |
Skip Test/Step | This toggle is disabled by default. When enabled, test case and test step skipping can be done during test plan execution. |
Tests | A test plan contains one or more test cases that are added when defining the plan. The number of tests and test steps contained in a test plan is automatically calculated and displayed in the plan view. |
Test Plan Views
View | Purpose |
|---|---|
Plan View | The Plan View lists the test plans belonging to a project. It is reached by selecting the Plan button in the set of T4J menus. |
Plan Tree View | The Plan Tree of a test plan displays the plan’s test cases hierarchically structured. It is reached by selecting the name of a test plan in the Plan View. The plan name is the name of the root folder of the tree structure. |
Execution View | The Execution View is a closely related view that displays the various executions of test plans in a project. It is reached by selecting the Execution button in the set of T4J menus. For details see Test Execution. |
Test Plan Operations
See Test Plans - How-to Guide.