Moving from Xray
Bring your Xray tests. Keep every Jira key.
Import Xray tests or Jira's export of them and see exactly what will happen before anything is saved. Folders, steps with their test data, and labels come across, and a newer export later updates the same tests.
Check file
- New
- 12
- Updated
- 3
- No change
- 0
- Skipped
- 0
15 tests in 4 subfolders · ready to import
Four steps
From export to running tests in one sitting.
No connection to Jira and no credentials: the import reads the export file you choose.
Export from Xray or Jira
Export the tests as Xray JSON, fetch them with Xray's GraphQL API, lay them out for the Test Case Importer, or use Jira's CSV export of the test issues.
Check the file
In TestPlum, go to Tests, Import, Xray and choose the file. You see how many tests are new, updated, unchanged or skipped, and anything that won't come across exactly.
Import
Nothing is written unless every test is valid. Files of more than 250 tests import in the background while you keep working, and you can cancel.
Import again while you switch
Export again whenever Xray changes. Tests are matched by Jira key, so only tests that changed are updated.
Four ways in
Whichever export you have.
TestPlum recognises the format, so you never have to say which one it is. Other JSON and generic CSV files are refused with a reason.
- 01
Xray JSON
The format Xray imports tests in bulk from, as Xray Cloud or Server writes it.
- 02
Xray GraphQL results
What Xray's GraphQL API returns for tests, with Jira's rich text read as plain text.
- 03
Test Case Importer CSV
One row per step, laid out for Xray's Test Case Importer.
- 04
Jira CSV export
Jira's export of your test issues, with the steps held as JSON in the Manual Test Steps field.
What comes across
Everything in the export has a place.
Each part of an Xray export and where it lands. Anything that can't come across exactly is listed in the check before you import.
| In the Xray export | In TestPlum |
|---|---|
| Test repository folder, such as /Checkout/Payments | Folder and subfolders, in the same nesting |
| Jira key (SHOP-12) | Kept with the test, so a newer export updates it instead of adding a copy |
| Summary | Title |
| Description, including Jira rich text | Description, as text |
| Steps: action, data and expected result | Steps with their expected result; the test data stays with its step |
| Preconditions | Preconditions |
| Priority, including Highest and Lowest | Priority: critical, high, medium or low |
| Labels | Tags, replacing the test's tags on each import |
| Requirements a test covers (Tests links in Jira's CSV) | References |
| Cucumber scenario | Kept in the description, as GherkinCucumber tests have no steps here; the check says which tests this applies to. |
| Generic test definition | Kept in the description |
| Components and other fields | A custom field with the same name, otherwise kept in the description |
| Jira bookkeeping (status, assignee, dates) and Xray's computed fields | Left out: they describe Jira, not the test |
What stays in Xray
Step-by-step results
Each test's result in an execution comes across, with its date, tester, comment and defects; the status of each step stays in Xray.
Test plans and test sets
Create cycles and runs for them as you go; new runs start from a suggested selection.
Attachments and inline images
Images in Jira text stay in Jira. The check tells you which tests have them.
After the move
Your tests, outside the ticket queue.
Tests stop being Jira issues among the rest, and results lead to one answer: whether the release is ready.
- 01
A release verdict
Ready or not ready from checks you agree in advance, with a link to resolve each failing one. The release verdict
- 02
Passes weighed by proof
A pass on retry, from a flaky test or with no assertions counts only partly in the trusted pass rate.
- 03
Bugs still go to Jira
Send a bug from TestPlum to a connected Jira project with one click; its link is kept on the bug.
- 04
Manual and automated together
Playwright runs, JUnit from any CI and manual results land in the same runs. For developers
- 05
Coverage you can trust
Requirements count as verified only when their tests pass on solid evidence. Test management
- 06
Alerts where your team talks
Slack and Microsoft Teams hear when a run is signed off, automated tests fail or the verdict changes.
Do my Jira keys change?
No. Each test keeps its Jira key, such as SHOP-12, as its external ID, so importing a newer export finds the same tests and updates only what changed. Tests also get a TestPlum key for use inside TestPlum.
Which Xray exports can I use?
Xray's bulk import JSON, the JSON its GraphQL API returns for tests, a CSV laid out for Xray's Test Case Importer, or Jira's CSV export of the test issues with steps in the Manual Test Steps field. TestPlum recognises which one it is.
What happens to test data in my steps?
It stays with its step: the step shows the action with its data below it, and the expected result alongside.
What about Cucumber and Generic tests?
They have no steps in TestPlum, so the Cucumber scenario or the generic definition is kept in the test's description, and the check lists which tests this applies to.
Are executions, test plans and test sets imported?
Executions are. After importing the tests, import Xray's JSON results (or the test runs its GraphQL API returns) under Tests, Import, Xray, Past results: each execution becomes a signed-off run dated as it happened, matched by Jira key, and importing it again changes nothing. Test plans and test sets stay in Xray.
Can I bring TestRail tests into the same project?
Yes. Xray tests are matched by Jira key and TestRail tests by their C-number, so the two never collide, and each source can be imported again later.
Does TestPlum connect to Jira or Xray?
Not for importing: the import reads export files, so no Jira or Xray credentials are needed for it. Separately, bugs can be sent from TestPlum to a Jira project you connect.
How large can an export be?
Up to 5,000 tests per file. Files of more than 250 tests import in the background with progress you can follow on any page.
Xray and Jira are trademarks of their owners. TestPlum is not affiliated with or endorsed by them; the names are used only to describe the export files TestPlum can import.
Import your first Xray tests
Create a workspace, export a folder of tests from Xray or Jira and check it. Nothing is saved until you choose to import.