Versions Compared

Old Version 3

changes.mady.by.user Support Advocate (ease solutions)

Saved on

compared with

New Version 4

changes.mady.by.user Support Advocate (ease solutions)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel

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. 


NameThe name identifies the execution together with a unique id.
It's required and has to be set during creation of the execution. It can be edited later.
The names of executions in the same project don't need to be unique. 
DescriptionAn optional description for further explanation of the test execution.
The description can be set during creation of the execution and can be edited later. 
AssigneeA user the test execution is assigned to.
The assignee can be set during creation of the execution and can be edited later. 
ProjectA project linked to the execution.
Allows to link the execution to projects other than the corresponding project of the test / test plan.
The corresponding project of the test / test plan is selected by default.
The linked project can be set during creation of the execution and can be edited later. 
Component/s

One or more project components linked to the execution.
To link components the project property has to be set.
Components always come from the same project set in the project property.
The linked components can be set during creation of the execution and can be edited later. 

Fix Version/s

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. 

Creation DateThe date and time the execution was created.
The value of this property is automatically set after the execution was created and can't be changed. 
Start DateThe date and time the execution was first started.
The value of this property is automatically set after the execution was started and can't be changed. 
Execution Date

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.

Status

The status of the execution. The value of this property is automatically set.
The following execution status exist:

  • Image Modified Not executed
  • Image Modified Running
  • Image Modified Failed
  • Image Modified Passed
TestsAn execution contains all test of the test plan it was created on. In case of a single test execution it contains only the one test executed.
The tests contained in the execution won't change although the corresponding test plan might be changed later. 
Test StepsAn execution contains all test steps that are part of the included tests at the time creating the execution.
The test steps contained in the execution won't change although the definition of the corresponding tests might be changed later.
Result & Status
for each test / test step		An execution contains a status and a result description for each contained test and test step.
These properties are further described in the Execution Runner and Statistics Reference. 
Panel

Test Execution - User interface

The execution view is one of the four main views in Test for JIRA.
After selecting a project in the plugin section you can navigate to the execution view by clicking the Execution button in the top right corner.

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.
Hovering the mouse over the indicator displays the status, name and execution date of the completed executions.
If executions exist for a test plan that was later deleted, the test plan and its executions are still displayed in the test plan executions section.
The plan name of a deleted test plan is colored in grey.

For every test execution of a test plan the following properties are displayed:

  • Execution Name
  • Status
  • The most recent date from creation date, start date and execution date
  • The assignee of the execution 

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.
The definition tree of the selected project might contain tests created on different projects. These tests would be displayed in the execution view of the project they were created on.
Executions displayed in the section don't necessarily have to be created from the definition tree of 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:

  • Execution Name
  • Status
  • The most recent date from creation date, start date and execution date
  • The assignee of the execution

...

Panel

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:
 


Affected section:test plan executionssingle test executions
Hide Plan ExecutionsHides all test plan executions. Disables the "Plan Name" option.

Image Modified

Image Modified

Hide Single Test ExecutionsHides all single test executions. Disables the "Issue Summary" option.

Image Modified

Image Modified

Plan NameDisplays only test plans in the test plan execution section containing the provided query in their names.

Image Modified

Image Modified

Issue SummaryDisplays only tests in the single test execution section containing the provided query in their issue summary.

Image Modified

Image Modified

Execution NameDisplays only executions containing the provided query in their execution name.

Image Modified

Image Modified

StatusDisplays only executions with the selected status.

Image Modified

Image Modified

AssigneeDisplays only executions with the selected assignee.

Image Modified

Image Modified

ProjectDisplays only executions having the project property set to the selected project. 

Image Modified

Image Modified

Component/sDisplays only executions having the component/s property set to the selected component/s. Works only in combination with the project option.

Image Modified

Image Modified

Fix Version/sDisplays only executions having the fixed version/s property set tot the selected fix version/s.

Image Modified

Image Modified

Execution From DateDisplays only executions created after the selected date.

Image Modified

Image Modified

Execution To DataDisplays only executions created before the selected date.

Image Modified

Image Modified

Panel

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

Export formatContent
XMLThe resulting file contains detailed information about every test plan execution including executions of deleted plans.
It also contains detailed information about the corresponding test plan for every execution included.
The XML export also provides information such as item ids that can be used to integrate another application with T4J via its REST API. 
Excel

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
Code Block
languagexml
titleExample XML export
collapsetrue
<?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 executions

Export formatContent
XMLThe resulting file contains the same information about every execution that it does when exporting test plan executions.
Instead of information about test plans the file contains detailed information about the corresponding test for every execution included. 
Excel

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
Code Block
languagexml
titleExample XML export
collapsetrue
<?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>
                <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>
                <issueSummary>Example test</issueSummary>
                <issueUrl>http://host:port/jira/browse/PRJ-20</issueUrl>
            </single>
        </execution>
    </executions> 


Last execution details

Export formatContent
XMLThe resulting file contains detailed information about every test plan including deleted plans and their last execution.
This result is similar to the content when exporting test plan executions or single test executions
but additionally it contains detailed information about the tests of each execution.
Excel

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
Code Block
languagexml
titleExample XML export
collapsetrue
<?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>&lt;p&gt;An example test&lt;/p&gt;</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>