Versions Compared

Key

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

...

Panel

Definition Tree - Export

Click on the Export button to open the export menu.
Select an export format from the list to export the definition tree content to.
The exported content depends on the type of the item currently selected.
An applied filter also affects the exported content.

The following tables describe the export content in each format depending on issue type and applied filter.

Since the XML export provides information that can be used to integrate another application with T4J via its REST API a complete example export file is provided.
The example file is the result of an export with the root folder of the definition tree selected and no filter applied. It covers the structure of the root item, a folder item and a test item.
Note that there's no example export for Excel and Word since those export formats are mostly used for internal documentation purposes. Therefore a textual description of the content should be sufficient. 

Plan Tree - Export formats

XML

Type of the selected tree itemContentFilter applied
Test itemDetailed information about the selected test item including item ids that can be used for REST API calls.


Contains the same information stated above.

Tree folderContains no information except for the following items: <trees><tree/></trees> 


Detailed information about the selected tree folder and all subsequent folders and contained test items.

Root folder or nothing selectedDetailed information of the root folder.


The content is equivalent to the content when selecting a tree folder just with the root folder as top level element. 


Code Block
languagexml
titleExample response
collapsetrue
<?xml version="1.0" encoding="UTF-8"?>
    <trees>
        <tree>
            <folders>
                <name>PROJECT</name>
                <description/>
                <id>-1</id>
                <nameDisplay>PROJECT</nameDisplay>
                <parent>-2</parent>
                <folders>
                    <name>Example Folder</name>
                    <description>An example folder</description>
                    <id>658</id>
                    <nameDisplay>Example Folder</nameDisplay>
                    <parent>-1</parent>
                    <folders>
                        <name>Subfolder</name>
                        <description>A subfolder of the example folder.</description>
                        <id>668</id>
                        <nameDisplay>Subfolder</nameDisplay>
                        <parent>658</parent>
                        <issues>
                            <id>1000</id>
                            <issueId>12300</issueId>
                            <key>PRJ-20</key>
                            <url>http://host:port/jira/browse/PRJ-20</url>
                            <summary>ExampleTest</summary>
                            <description>test description</description>
                            <descriptionHTML>&lt;p&gt;test description&lt;/p&gt;</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 - Hidden Job Switch</name>
                                    <value>false</value>
                                </attribute>
                            </attributes>
                            <links>
                                <link>
                                <linkName>is blocked by</linkName>
                                <issueKey>PRJ-17</issueKey>
                                <issueSummary>Linked Issue</issueSummary>
                                <issueUrl>http://host:port/jira/browse/PRJ-17</issueUrl>
                                <priority>Major</priority>
                                <status>To Do</status>
                                </link>
                            </links>
                            <teststeps>
                                <teststep>
                                    <id>53</id>
                                    <name>Example Test Step</name>
                                    <description>An example test step using parameter p1: ##p1##</description>
                                    <result>The expected result.</result>
                                </teststep>
                            </teststeps>
                            <parameters>
                                <parameter>
                                    <key>p1</key>
                                    <value>parameter value</value>
                                </parameter>
                            </parameters>
                            <path>Example Folder</path>
                            <path>Subfolder</path>
                            <combinedPath>\PRJ\Example Folder\Subfolder</combinedPath>
                        </issues>
                        <position>1</position>
                    </folders>
                    <position>1</position>
                </folders>
                <position>0</position>
            </folders>
        </tree>
    </trees>


Excel

Type of the selected tree itemContentFilter applied
Test itemContains basic information about the selected issue. Also contains information about issue links, test steps,
parameters and custom JIRA issue fields. 


Contains the same information stated above.

Tree folderContains no information.


Contains the name of the selected folder. Contains the folder path for all issues contained in the selected folder
and subsequent folders. Also contains basic informations for those issues and information about the test steps. 

Root folder or nothing selectedContains the name of the project.


The content is equivalent to the content when selecting a tree folder just with the root folder as top level element.


Word

Type of the selected tree itemContentFilter applied
Test itemContains basic information about the selected test item. Also contains information about issue links, test steps,
parameters and custom JIRA issue fields. 


Contains the same information stated above.

Tree folderContains no information.


Contains the name of the selected folder and all subsequent folders and basic information about the
contained issues. 

Root folder or nothing selectedContains the name of the project.


The content is equivalent to the content when selecting a tree folder just with the root folder as top level element.



Returns the issues/tests that are contained in a specific folder in the definition tree of a project.

Syntax

Panel

Searching for tests

Advanced search integration

The advanced search functionality of JIRA allows to use structured queries to search for issues. These queries are written in Atlassian's JIRA Query Language (JQL). The result set is displayed as a list of issues in the issue navigator. It is also possible to save advanced search queries for private or public use.

Test for JIRA enhances the advanced search of JIRA with new functions to search for issues in T4J specific entities such as test plans or definition trees.

Saved JQL queries can be further used for filtering or adding issues matching the query to a definition tree.

How to search for tests

  1. Select Issues > Search for Issues from the main navigation bar
  2. Switch to advanced searching by clicking the Advanced link from the filter bar
  3. Enter a query in the search text box
  4. Click on the Search button or hit enter to execute the query
Info

The query should be of the following structure: field operator function()

You can look up the supported fields and operators for the new Requirements for JIRA functions in the function reference below.

Function Reference

Test Definition Folder

Expand
Code Block
themeConfluence
firstline1
linenumberstrue
testDefinitionFolder(path)

Where path represents a part of the hierarchical structure of the definition tree.

Path should be of the following form: "project name/parentFolder/.../childFolder" 

Supported Fields

Supported Operators

=!=~!~>>=<<=ISIS NOTINNOT INWASWAS INWAS NOTWAS NOT INCHANGED(error)(error)(error)(error)(error)(error)(error)(error)(error)(error)(tick)(tick)(error)(error)(error)(error)(error)Examples

Find all issues that are contained in the folder "Webtests" within the definition tree of the project "OnlineHotelReservation:

Code Block
themeConfluence
firstline1
linenumberstrue
issue in testDefinitionFolder("OnlineHotelReservation/Webtests")

Test Definition Path

Expand

Returns the issues/tests that are contained in a specific folder in the definition tree of a project.
Also returns the issues/tests of subsequent folders.

Syntax

Code Block
themeConfluence
firstline1
linenumberstrue
testDefinitionPath(path)

Where path represents a part of the hierarchical structure of the definition tree.

Path should be of the following form: "project name/parentFolder/.../childFolder" 

Supported Fields

Supported Operators

=!=~!~>>=<<=ISIS NOTINNOT INWASWAS INWAS NOTWAS NOT INCHANGED(error)(error)(error)(error)(error)(error)(error)(error)(error)(error)(tick)(tick)(error)(error)(error)(error)(error)

Examples

Find all issues that are contained in the folder "Webtests" or one of its subfolders within the project "OnlineHotelReservation:

Code Block
themeConfluence
firstline1
linenumberstrue
issue in testDefinitionPath("OnlineHotelReservation/Webtests")

Test Plan

Expand

Returns all issues/tests that are part of a specific test plan.

Syntax

Code Block
themeConfluence
firstline1
linenumberstrue
testPlan(project,plan)

Where project is the name of the project that contains the desired test plan and plan is the name of the test plan.

Supported Fields

Supported Operators

=!=~!~>>=<<=ISIS NOTINNOT INWASWAS INWAS NOTWAS NOT INCHANGED(error)(error)(error)(error)(error)(error)(error)(error)(error)(error)(tick)(tick)(error)(error)(error)(error)(error)

Examples

Find all issues/tests that are part of the test plan "Example Plan" created on the project "OnlineHotelReservation":

Code Block
themeConfluence
firstline1
linenumberstrue
issue in testPlan("OnlineHotelReservation","Example Plan")

Failed in Execution

Expand

Returns all issues/tests that are marked as failed in a specific execution of a given test plan.

Syntax

Code Block
themeConfluence
firstline1
linenumberstrue
failedInExecution(project,plan,execution)

Where project is the name of the project that contains the desired test plan.
Plan is the name of the test plan.
Execution is the name of a specific execution of the given test plan.

Supported Fields

Supported Operators

=!=~!~>>=<<=ISIS NOTINNOT INWASWAS INWAS NOTWAS NOT INCHANGED(error)(error)(error)(error)(error)(error)(error)(error)(error)(error)(tick)(tick)(error)(error)(error)(error)(error)

Examples

Find all issues/tests that are part of the test plan "Example Plan" created on the project "OnlineHotelReservation", which were marked as failed during "Test Execution":

Code Block
themeConfluence
firstline1
linenumberstrue
issue in failedInExecution("OnlineHotelReservation","Example Plan","Test Execution")

T4J provides custom JQL to enable searching integrated issues in Jira.

See Advanced search integration to know more.