Targeting existing issues⚓︎
The plugin does not upload any results unless you reuse existing Jira issues to not clutter up your projects with unnecessary test case (or test execution) issues. This section teaches you everything you need to know to target such existing issues.
Reuse Cypress issues⚓︎
To link Cypress tests to Jira issues, simply add the test case issue's key anywhere in the name of the innermost it()
function (or corresponding alternatives like specify()
):
The plugin parses all test case names and looks for sequences of the form
<projectKey>-<number>
, with <projectKey>
being the configured project key and <number>
the issue number.
Reuse Cucumber issues⚓︎
To link your Cucumber feature files to existing Jira issues, you need to tag both scenario (outlines) and backgrounds. The tagging schemes follow the schemes Xray expects when importing feature files (see here or here).
Test issues⚓︎
In feature files, you must annotate scenarios (or scenario outlines) with a tag containing the corresponding test case issue key. The tag's prefix must match the one configured in your Xray settings (see here).
Precondition issues⚓︎
In feature files, you must add a comment to a background's very first step containing the tag for a corresponding precondition issue key. The tag's prefix must match the one configured in your Xray settings (see here).
Note
You can find more information about preconditions here for Xray server and here for Xray cloud.
Reuse test execution issues⚓︎
By default, the plugin will always create a new test execution issue whenever you upload test results.
You can prevent that from happening by specifying the test execution issue key you want to attach the results to.