Moving from TestRail
Bring your TestRail tests. Keep every ID.
Import a TestRail export and see exactly what will happen before anything is saved. Sections, steps and fields come across, each test keeps its C-number, and a newer export later updates the same tests.
Check file
- New
- 6
- Updated
- 0
- No change
- 0
- Skipped
- 0
6 tests in 5 subfolders · ready to import
Four steps
From export to running tests in one sitting.
No connection to TestRail and no credentials: the import reads TestRail's own export file.
Export from TestRail
Open the test suite, choose Export, then XML. XML keeps every section, step and field; a CSV with separated steps works too.
Check the file
In TestPlum, go to Tests, Import, TestRail 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 TestRail changes. Only tests that changed are updated, or you can leave already imported tests as they are.
What comes across
Everything in the export has a place.
Each part of a TestRail export and where it lands. Anything that can't come across exactly is listed in the check before you import.
| In the TestRail export | In TestPlum |
|---|---|
| Test suite | A folder named after the suite, or a name you choose |
| Sections and subsections | Subfolders, in the same order, including empty ones |
| Case ID (C123) | Kept with the test, so a newer export updates it instead of adding a copy |
| Separated steps | Steps, each with its expected result |
| Text template steps and expected result | Steps |
| Exploratory mission and goals | The test's description |
| Preconditions | Preconditions |
| Priority (by name or on the 1–5 scale) | Priority: critical, high, medium or low |
| Type | The test type with the same nameIf your organization doesn't have that type yet, it is left empty and the check says so. |
| Estimate, such as 1m 30s | Estimate in minutes, rounded up |
| References | References |
| Other custom fields | A custom field with the same key or label, otherwise kept in the description |
What stays in TestRail
Screenshots and files on results
Each past result comes across with its status, date, tester, comment and defects; files attached to it stay in TestRail.
Images pasted into text
They link back to your TestRail site. The check tells you which tests have them.
Users, plans and milestones
Invite your team, then create cycles and runs as you go.
After the move
Same tests. A clearer answer.
Your tests arrive organised the way you had them. What changes is what you can do with the results.
- 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
Failures sorted by cause
Failures are grouped and sorted as product bug, broken test, environment or flaky, with the reasons. Understanding failures
- 04
Manual and automated together
Playwright runs, JUnit from any CI and manual results land in the same runs. For developers
- 05
Suggested runs
New runs start from what failed last time, never ran, changed since it ran or is critical.
- 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 TestRail IDs change?
No. Each test keeps its TestRail case ID (C123) as its external ID, so importing a newer export finds the same tests and updates only what changed. Tests also get a TestPlum key, such as SHOP-C12, for use inside TestPlum.
Can I import several test suites?
Yes. Export and import each suite. By default each suite becomes a folder with its own name, or you can choose the folder name when you import.
How large can an export be?
Up to 5,000 tests per file. Export a large suite one section at a time if it has more. Files of more than 250 tests import in the background with progress you can follow on any page.
Are past runs and results imported?
Yes. After importing the tests, export a test run from TestRail as CSV with at least the Case ID and Status columns, and import it under Tests, Import, TestRail, Past results. Each run becomes a signed-off run dated as it happened, with each result's tester, comment, time and defects. It adds to each test's history but never changes the release verdict, and importing the same run again changes nothing.
What happens to images in my test steps?
Images pasted into TestRail text are links back to your TestRail site, so they stay there. The check lists how many tests contain them, so you can re-attach the ones you need.
Can we keep using TestRail while we switch?
Yes. Import a newer export as often as you like: tests are matched by their TestRail ID, unchanged tests are left alone, and you can choose not to overwrite tests you have already edited in TestPlum.
Does TestPlum connect to TestRail's API?
No. The import reads TestRail's own XML or CSV export, so no TestRail credentials are needed or stored.
What if part of the file is invalid?
Nothing is written. The check lists every problem with the test it belongs to, so you can fix it in TestRail and export again.
TestRail is a trademark of its owner. TestPlum is not affiliated with or endorsed by it; the name is used only to describe the export files TestPlum can import.
Import your first TestRail suite
Create a workspace, export one suite from TestRail and check it. Nothing is saved until you choose to import.