Move in without starting over
Bring your tests from TestRail, Xray or a spreadsheet. TestPlum shows you what will happen before anything is saved, keeps the folder structure and IDs, and lets you import a newer export later without duplicates.
Check file
- New
- 6
- Updated
- 0
- No change
- 0
- Skipped
- 0
6 tests in 5 subfolders · ready to import
Every import
Checked first. Written only when it is all right.
Upload the export
Pick the file under Tests, Import. TestPlum recognises the format.
See what will happen
New, updated, unchanged and skipped tests are counted, and anything that will not come across exactly is listed.
Fix or go
If any test is invalid, nothing is written and every problem is shown with its test.
Keep working
Large files import in the background with progress you can follow from any page, and cancel. All of it lands, or none of it.
Import again later
IDs are kept, so a newer export updates the same tests instead of adding copies.
01 From TestRail
TestRail
XML or CSV export of a test suite. Each test keeps its TestRail ID, so a newer export updates the same tests.
The full TestRail guideWhat comes across
- Sections, in order, including empty ones
- Steps, preconditions and expected results
- Priorities (also the 1–5 scale), types, estimates and references
- Exploratory missions and goals
- Other fields, into matching custom fields or the description
02 From Xray
Xray
Xray's JSON, its GraphQL results, the Test Case Importer CSV or Jira's CSV export. Each test keeps its Jira key, so a newer export updates the same tests.
The full Xray guideWhat comes across
- Repository folders as folders
- Steps with their test data
- Labels as tags and Jira priorities
- Requirement links as references
- Cucumber scenarios and generic definitions in the description
03 From Any CSV
Any CSV
A spreadsheet with one row per step. Rows with an external ID update the matching test instead of adding a copy.
What comes across
- Title, folder and subfolder
- Priority, type, estimate and tags
- Preconditions and description
- Steps and expected results
- Custom fields by key or label
How do I export my tests from TestRail?
In TestRail, open the test suite, choose Export, then XML or CSV. XML keeps every section, step and field; CSV with separated steps works too. Upload the file in TestPlum under Tests, Import, TestRail.
How do I export my tests from Xray?
Export the tests as JSON (Xray's import format, or the result of its GraphQL API), as a CSV laid out for Xray's Test Case Importer, or use Jira's CSV export of the test issues. Upload it in TestPlum under Tests, Import, Xray.
What happens if I import the same file twice?
Nothing changes. Each test keeps its TestRail ID or Jira key, so a second import of the same file finds every test unchanged, and a newer export updates only what changed.
Are past test results imported?
Yes, from TestRail and Xray. Import the tests first, then a TestRail run's CSV export or Xray's results. Each run becomes a signed-off run dated as it happened, with each result's tester, comment and defects. History adds to each test's record but never changes the release verdict, and a run imported before is skipped.
What if part of my file is invalid?
Nothing is written. The check lists every problem with the test it belongs to, so you can fix the export and try again. Up to 5,000 tests per file.
What happens with a large export?
Files of more than 250 tests are imported in the background after the check, so you can keep working. A progress card follows you around the project, you can cancel at any time, and a cancelled or failed import changes nothing. You are notified when it finishes.
Import your first suite today
Create a workspace, open Tests and choose Import. The check runs before anything is saved, so trying it costs nothing.