...
| Panel | ||
|---|---|---|
| ||
Test Execution - Reference pages Global Test Execution Reference
|
...
Test Execution - Properties
The table below contains all properties and contained data of a test execution.
The properties of a test plan execution and a single test execution are identical except that a test plan execution can contain multiple tests while a single test execution contains exactly one test.
...
Test Execution Attributes
Name | The name identifies the test execution, which is set during creation of the execution, but can be changed at any time. The names of executions do not need to be unique. |
Description | An optional description |
...
to document the test execution. |
...
Assignee | The user to which the test execution is assigned |
...
. |
...
Project | A project linked to the test execution. |
...
This is by default the project in which the execution is created, but a different project can be selected. The execution belongs to the project in which it is created, regardless of the selected project. | |
Component/s | One or more project components from the linked |
...
On or more fix versions linked to the execution.
To link fix versions the project property has to be set.
Fix versions always come from the same project set in the project property.
The fix versions can be set during creation of the execution and can be edited later.
...
The date and time the execution was completely finished.
The value of this property is automatically set after the execution was completed and can't be changed.
...
The status of the execution. The value of this property is automatically set.
The following execution status exist:
Not executed
...
| Panel |
|---|
Test Execution - User interfaceThe execution view is one of the four main views in Test for JIRA. The execution view is divided into the following two sections: Test Plan Executions The test plan executions section displays all test plans of the selected project and all corresponding test executions in form of a table. For every test plan the plan name is displayed and a small indicator comparing the amount of passed executions against the amount of failed executions for the test plan. For every test execution of a test plan the following properties are displayed:
Single Test Executions The single test executions section displays all tests of the selected project that have at least one single test execution. The section displays only tests created on the selected project. If single executions exist for a test that was later deleted neither the test nor its previous executions will be displayed. For every test the issue key and summary is displayed. For every single test execution of a test the following properties are displayed:
|
...
Test Execution - Operations
The test execution view provides the same operations for both test plan executions and single test executions.
Add execution
Click on the Add Execution next to the name of a test plan to open the add execution dialog.
Obviously the button is only visible for existing test plans.
Within the dialog you can enter the values for the following properties:
- Name
- Description
- Assignee
- Project
- Components
- Fix Versions
Click Create to create the execution so it can be run later.
You can also create and instantly run an execution by clicking Execute.
Run/Continue execution
Click on the next to an execution you want to run or continue.
The icon is only visible for executions that aren't already finished.
Clicking the icon opens the test execution runner with the last saved state of the selected execution.
Display execution statistics
Click on the next to an execution to display the corresponding execution statistics.
Note that statistics are also available for test executions currently in progress.
Edit the metadata of an execution
Click on the next to an execution to open the edit execution dialog.
The dialog allows you to edit the same properties that can be set during creation of a test execution.
Note that you can only edit the metadata of an execution.
The status of a test or test step can't be changed after it has been set.
Delete execution
Click on the next to an execution to open the delete execution dialog.
Deleting the only execution of a deleted test plan will also remove the test plan test plan executions table.
Deleting the only execution of a single test will also remove the test from the single test executions table.
...
Test Execution - Filter
Click on the Filter button to open the filter input.
Select one or more filter options and click Filter to apply the filter. An orange warning symbol next to the Test Plan Executions header indicates that a filter is applied.
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.
There are different filter settings that affect either the displayed test plan executions or the single test executions or both sections.
The different settings and the affected section/s are documented in the table below:
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Test Execution - Export
Click on the Export button to open the export menu.
Select an export format for the group of executions you want to export from the list.
You can choose between exporting
- all test plan executions
- all single test executions
- execution details for the latest test execution
The executions can be exported as XML or Excel file.
The following tables describe the export content in each format for the three execution groups.
Export formats and content
Test plan executions
...
The resulting file contains the name of the project and information about all test plan executions including executions of deleted test plans.
For each test plan execution the file contains the following information:
- The name of the corresponding test plan
- The execution name
- Status of the execution
- Date and time the execution was created
- Date and time the execution was started
- Date and time the execution finished
- The assignee of the execution
...
| language | xml |
|---|---|
| title | Example XML export |
| collapse | true |
...
project. | |
Fix Version/s | One or more fix versions from the linked project. |
Creation Date | The date and time the test execution is created. These are automatically set during creation and cannot be changed. |
Start Date | The date and time the test execution is first started. This is automatically set at the start of the execution and cannot be changed. |
Execution Date | The date and time the test execution is completely finished. This is automatically set at the end of the execution and cannot be changed. |
Status | The status of the test execution. This is automatically set with the following values:
|
Tests | The test cases included in the test execution, which depends on the type of the execution:
The execution’s test cases never change even if the test cases in the corresponding test plan are subsequently changed. |
Test Steps | The test steps included in the test execution’s test cases. The execution’s test steps never change even if the test steps in the corresponding test cases are subsequently changed. |
Result & Status | A test execution includes a status and a result description for each included test case and test step. |
Test Execution Views
View | Purpose |
|---|---|
Execution View | The Execution View displays the various executions of test plans in a project. It is reached by selecting the Execution button in the set of R4J menus. The Execution View is split into two tables, one organized by test plan executions and the other by single test case executions. Various attributes of executions are displayed: test plan name, execution name, status, date of execution, assignee. In the case of test plan executions, a “last executions” bar shows the proportion of successful versus failed executions of the test plan. Executions of a test plan that was subsequently deleted are still shown with the test plan name displayed as grey. Single executions of a test case that was subsequently deleted are not displayed. |
Plan View | The Plan View is a closely related view that lists the test plans belonging to a project. It is reached by selecting the Plan button in the set of R4J menus. For details see Test Plans. |
Test Execution Operations
See Test Execution - How-to Guide.
Test Execution Filter Criteria
Criteria | Purpose |
|---|---|
Hide Plan Executions | Hide all test plan executions. Disables the "Plan Name" option. |
Hide Single Test Executions | Hide all single test case executions. Disables the "Issue Summary" option. |
Plan Name | Display executions in the test plan execution section whose plan name matches the provided string. |
Issue Summary | Display executions in the single test execution section whose issue summary matches the provided string. |
Execution Name | Display executions whose name matches the provided string. |
Status | Display executions with the selected status. |
Assignee | Display executions with the selected assignee. |
Project | Display executions linked to the selected project. |
Component/s | Display executions with the selected component/s in the linked projects. |
Fix Version/s | Display executions with the fixed version/s property set totthe selected fix version/s in the linked projects. |
Execution From Date | Display executions created after the selected date. |
Execution To Data | Display executions created before the selected date. |
Test Execution Export
Test plan executions
Export format | Content |
XML | The resulting file contains detailed information about test plan executions (including executions of deleted plans), as well as detailed information about the corresponding test plans. The export also provides item IDs that can be used to integrate another application via the T4J REST API. |
Excel | The resulting file contains information about test plan executions (including executions of deleted test plans). For each execution there is a row with the following columns:
|
Single test case executions
Export format | Content |
XML | The resulting file contains detailed information about test plan executions. The export also provides item IDs that can be used to integrate another application with via the T4J REST API. |
Excel | The resulting file contains information about single test case executions. For each execution there is a row with the following columns:
|
Last execution details
Export format | Content |
XML | The resulting file contains detailed information about the test cases and test tests of the last executions of test plans (including executions of deleted plans). The export also provides item IDs that can be used to integrate another application with via the T4J REST API. |
Excel | The resulting file contains the names of test plans (including executions of deleted plans) and detailed information about the last execution for each plan, as follows:
|
Examples of XML exports
Test plan execution
| Code Block |
|---|
<?xml version="1.0" encoding="UTF-8"?> <executions> <projectName>PROJECT</projectName> <execution> <result> <id>47</id> <name>Example test execution</name> <description>An example test execution</description> <deleted>false</deleted> <assignee>admin</assignee> <passed>true</passed> <failed>false</failed> <running>false</running> <notrun>false</notrun> <created>2016-10-27T12:44:24.050+02:00</created> <started>2016-10-27T12:56:00.777+02:00</started> <finished>2016-10-27T12:56:00.777+02:00</finished> </result> <plan> |
...
|
...
<prjKey>PRJ</prjKey> |
...
<project>10100</project> |
...
<description/> |
...
<configuration>0</ |
...
configuration> |
...
<id>81</ |
...
id> <name>Example |
...
plan</ |
...
name> |
...
<copying>false</ |
...
copying> |
...
<copyFailed>false</ |
...
copyFailed> |
...
<testCount>2</ |
...
testCount> |
...
<stepCount>2</stepCount> </plan> |
...
</execution> <execution> |
...
<result> |
...
|
...
<id>48</id> |
...
<name>Example execution 2</name> |
...
<description/> |
...
<deleted>false</ |
...
deleted> |
...
<assignee>admin</ |
...
assignee> |
...
<passed>true</ |
...
passed> |
...
<failed>false</ |
...
failed> |
...
<running>false</ |
...
running> |
...
<notrun>false</ |
...
notrun> |
...
<created>2016-10-27T12:57:17.250+02:00</created> |
...
<started>2016-10-27T12:57:26.290+02:00</started> |
...
|
...
<finished>2016-10-27T12:57:28.273+02:00</finished> |
...
</result> <result> |
...
<id>46</id> |
...
<name>Another execution |
...
of the same test plan</name> <description/> <deleted>false</deleted> <assignee>admin</assignee> <passed>true</passed> <failed>false</failed> <running>false</running> <notrun>false</notrun> <created>2016-10- |
...
26T15: |
...
06: |
...
01. |
...
997+02:00</created> <started>2016-10- |
...
26T15: |
...
06: |
...
12. |
...
793+02:00</started> <finished>2016-10- |
...
26T15: |
...
06: |
...
29. |
...
680+02:00</finished> </result> |
...
<plan> |
...
<prjKey>PRJ</ |
...
prjKey> |
...
<project>10400</project> |
...
|
...
|
...
|
...
|
...
|
...
<description>Another |
...
example testplan</description> |
...
<configuration>1</ |
...
configuration> |
...
<id>76</ |
...
id> <name>Example Plan |
...
2</ |
...
name> |
...
<copying>false</ |
...
copying> |
...
<copyFailed>false</ |
...
copyFailed> |
...
<testCount>3</ |
...
testCount> |
...
<stepCount>2</stepCount> </plan> |
...
</execution> </executions> |
Single test case execution
| Code Block |
|---|
<?xml version="1.0" encoding="UTF-8"?> <executions> |
...
<projectName>PROJECT</projectName> |
...
<execution> |
...
<result> |
...
<id>48</ |
...
id> |
...
<name>Example single test execution</name> |
...
...
|
...
<description/ |
...
> |
...
<deleted>false</ |
...
deleted> |
...
<assignee>admin</ |
...
assignee> |
...
<passed>false</passed> |
...
<failed>false</ |
...
failed> |
...
<running>false</ |
...
running> |
...
<notrun>true</ |
...
notrun> |
...
<created>2016-10-27T12:46:37.417+02:00</created> </ |
...
result> <result> |
...
...
Single test executions
...
The resulting file contains the name of the project and information about all single test executions for tests of this project.
For each execution the file contains the following information:
- The name of the corresponding test
- The execution name
- Status of the execution
- Date and time the execution was created
- Date and time the execution was started
- Date and time the execution finished
- The assignee of the execution
...
| language | xml |
|---|---|
| title | Example XML export |
| collapse | true |
...
<id>34</id> <name>Another single test execution</name> <description/> <deleted>false</deleted> <assignee>admin</assignee> |
...
<passed>true</passed> |
...
|
...
<failed>false</failed> |
...
<running>false</running> |
...
<notrun>false</ |
...
notrun> |
...
<created>2016-10-20T16:02:01.193+02:00</created> |
...
<started>2016-10-20T16:02:03.393+02:00</started> |
...
<finished>2016-10-20T16:02:03.393+02:00</finished> |
...
</result> <single> |
...
<issueKey>PRJ-20</issueKey> |
...
|
...
Last execution details
...
The resulting file contains the names of all test plans including deleted plans and detailed information about the last execution for each plan.
For each execution the file contains the following information:
- Information about tests contained in the execution:
- The plan tree path for the test in the corresponding test plan
- Issue key
- Status
- Issue type
- Summary
- Description
- Information about test steps of the contained tests:
- Test step name
- Description
- Expected result
- Execution status
- Execution date and time
- Assignee
...
<issueSummary>Example test</issueSummary>
<issueUrl>http://host:port/jira/browse/PRJ-20</issueUrl>
</single>
</execution>
</executions> |
Last execution details
| Code Block |
|---|
<?xml version="1.0" encoding="UTF-8"?>
<executions>
<projectName>PRJ</projectName>
<execution>
<result>
<id>47</id>
<name>Example test execution</name>
<description>An example test execution</description>
<deleted>false</deleted>
<assignee>Admin</assignee>
<passed>true</passed>
<failed>false</failed>
<running>false</running>
<notrun>false</notrun>
<created>2016-10-27T12:44:24.050+02:00</created>
<started>2016-10-27T12:56:00.777+02:00</started>
<finished>2016-10-27T12:56:00.777+02:00</finished>
<tests>
<name>Example Test</name>
<description>An example test</description>
<descriptionRendered><p>An example test</p></descriptionRendered>
<failureMessage/>
<folders>Example Folder</folders>
<folders>Subfolder</folders>
<failed>false</failed>
<passed>true</passed>
<notrun>false</notrun>
<skipped>false</skipped>
<steps>
<name>Example test step</name>
<description>An example test step</description>
<failureMessage/>
<failed>false</failed>
<passed>true</passed>
<notrun>false</notrun>
<skipped>false</skipped>
<expectedResult>-</expectedResult>
<run>2016-10-27T12:56:00.777+02:00</run>
<id>537</id>
<parameters>
<key>p1</key>
<identifier>##p1##</identifier>
<value>parameter value</value>
</parameters>
<originalDescription>An example test step</originalDescription>
<executedBy>Admin</executedBy>
<executedByUrl>http://host:port/jira/secure/ViewProfile.jspa?name=admin</executedByUrl>
</steps>
<finished>2016-10-27T12:56:00.777+02:00</finished>
<id>197</id>
<executedBy>Admin</executedBy>
<executedByUrl>http://host:port/jira/secure/ViewProfile.jspa?name=admin</executedByUrl>
<issueUrl>http://host:port/jira/browse/PRJ-20</issueUrl>
<issueKey>PRJ-20</issueKey>
<issueStatus>To Do</issueStatus>
<issueType>New Feature</issueType>
</tests>
</result>
<plan>
<prjKey>PRJ</prjKey>
<project>10400</project>
<description/>
<configuration>0</configuration>
<id>81</id>
<name>Example test plan</name>
<copying>false</copying>
<copyFailed>false</copyFailed>
<testCount>2</testCount>
<stepCount>2</stepCount>
</plan>
</execution>
</executions> |