19 April 2021


The Xporter for Jira team proudly announces the release of Xporter 6.9.0. This point release contains several new features and bug fixes.

If installing manually from the Atlassian Marketplace, please make sure you install the correct asset for your Jira version (i.e. 7.x, 8.x, datacenter) from the releases page.




Highlights for this release


Parameterized Tests

Test parameterization is a powerful practice that allows the same test to be executed multiple times with different parameters.

Parameters are similar to input values (variables) that can change with each execution.

Parameterized tests in Xray are defined just like any other test with the addition of some parameter names within the specification using the following notation:  ${PARAMETER_NAME}. This notation is used to reference parameters within the test steps.

All iterations for a given test are executed within the context of the same test run. The step parameters will be replaced by the corresponding iteration values.

Xporter allows exporting Test Runs parameters and iterations directly from:

  • Tests
  • Test Executions

Please, check the Xray integration documentation  here


Xray Custom Fields

Test Step Custom Fields

Xray allows configuring additional fields/columns for Test Step fields. This way you can fully customize the columns for your manual Test Steps hiding native fields, and providing new fields.
With this new version, Xporter allows exporting test steps custom fields using the same approach, which means, the placeholder with the custom field name.

Iterating over Test Steps Custom Fields:
#{for teststeps}
    ${TestSteps[n].Action}
    ${TestSteps[n].Data}
    ${TestSteps[n].ExpectedResult}
    ${TestSteps[n].DateCustomField}
#{end}

#Iterating over Test Runs
#{for testruns}
    #Iterating over Manual Test Steps from Test Run
    #{for r=TestRuns[n].TestStepsCount}
        DateCustomField: ${TestRuns[n].TestSteps[r].DateCustomField}
    #{end}
#{end}

Test Run Custom Fields

It is now possible to export  Test Run custom fields. These fields can be useful to add extra information to Test Runs, usually only available during or after executing Tests.

#Iterating over Test Runs
#{for testruns}
  ${TestRuns[n].TextRunCustomField}
#{end}

If your custom field type is a Number, Data or Date Time you can use formatting functions.

Export Sub Test Executions



New Features and Bug Fixes