...
| Panel | ||
|---|---|---|
| ||
Test Plans - Reference pages Global Test Plans Reference
|
...
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 |
...
Displayed properties for each test plan:
...
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 |
...
Test Plan - Operations
All operations can be accessed from the Plan View of a test project.
Create test plans
Click on the New Plan button to open the new plan dialog.
Within the dialog you can enter the initial property values.
Click Create to create the new test plan.
Edit test plans
Click on the 
to open the edit test plan dialog.
The dialog allows you to edit the following properties:
- Name
- Description
- Configuration
Delete test plans
Click on the 
to open the delete test plan dialog.
Note that deleting a test plan won't delete previous executions of this plan.
The plan will be displayed as disabled in the Execution View and its executions can be accessed as usual.
Unfinished executions of deleted test plans will have a status of 
Aborted.
Copy test plans
Click on the 
to copy the corresponding test plan.
The new test plan will be inserted right below the original test plan.
The property values are copied from the original test plan except for the name which is the original name with a "(copy)" appended.
Also is the complete test plan structure copied from the original test plan. This includes all folders and tests that are part of the test plan.
Executions of the original test plan won't be copied.
Filter test plans
Click on the Filter button to open the filter input.
Enter a filter query and click on Filter to apply the filter to the test plan table.
Click on Clear to remove the current filter and close the input.
Click on Cancel to close the input without changing the current filter settings.
Once a filter is applied only test plans containing the filter query in their names will be displayed in the test plans table.
Properties other than the Plan Name are not evaluated against the filter query.
An orange warning symbol located in the top left corner indicates that a filter is applied.
...
Test Plan - Export
Click on the Export button to open the export menu.
Select an export format from the list to export the test plans for the selected project.
Note that the exported files always contain all test plans although a filter might be applied.
Test Plan - Export formats
XML
Exports the test plans for the selected project as XML file.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="UTF-8"?>
<testplans>
<testplan>
<prjKey>PRJ</prjKey>
<project>10100</project>
<description>An example test plan</description>
<configuration>1</configuration>
<id>12</id>
<name>Example Test Plan</name>
<copying>false</copying>
<copyFailed>false</copyFailed>
<testCount>1</testCount>
<stepCount>1</stepCount>
</testplan>
<projectName>PROJECT</projectName>
</testplans> |
XML with details
Exports the test plans and their tree structures for the selected project as XML file.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="UTF-8"?>
<trees>
<tree>
<folders>
<name>Example Test Plan</name>
<description/>
<id>123</id>
<nameDisplay>Example Test Plan</nameDisplay>
<parent>-152</parent>
<folders>
<name>Subfolder</name>
<description>A subfolder of the root folder.</description>
<id>345</id>
<nameDisplay>Subfolder</nameDisplay>
<parent>123</parent>
<issues>
<id>1000</id>
<issueId>12300</issueId>
<key>PRJ-20</key>
<url>http://host:port/jira/browse/PRJ-20</url>
<summary>Example Test</summary>
<descriptionHTML/>
<iconUrl>http://host:port/jira/images/icons/issuetypes/newfeature.png</iconUrl>
<issueType>New Feature</issueType>
<position>1</position>
<status>To Do</status>
<statusUrl>http://host:port/jira/images/icons/statuses/open.png</statusUrl>
<priority>Major</priority>
<priorityUrl>http://host:port/jira/images/icons/priorities/major.png</priorityUrl>
<attributes>
<attribute>
<name>Custom - Job Checkbox</name>
<value>false</value>
</attribute>
</attributes>
<teststeps>
<teststep>
<id>53</id>
<name>Example Test Step</name>
<description>An example test step using parameter p1: ##p1##</description>
<result>-</result>
</teststep>
</teststeps>
<parameters>
<parameter>
<key>p1</key>
<value>value</value>
</parameter>
</parameters>
<path>Subfolder</path>
<combinedPath>\PRJ\Subfolder</combinedPath>
</issues>
<position>1</position>
</folders>
<position>0</position>
</folders>
</tree>
</trees> |
Excel
Exports the test plans for the selected project as Excel file.
...
| title | Example Response |
|---|
Test Plans PROJECT
...
Excel with details
Exports the test plans and their tree structures for the selected project as Excel file.
...
| title | Example Response |
|---|
Example Plan
...
An example test step using parameter p1: ##p1##
...
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.