Enterprise DNA

Instead of TestRail

Stop renting TestRail. Own your test management system.

We build your version around your release process, bring your TestRail case library across and run it for you through Omni by Enterprise DNA. Start with the records your team needs to trust a release.

TestRail Enterprise lists US$78 per user per month, billed annually. That is US$936 per user per year.

Book a 30-minute test-tool bill review See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription buys

TestRail charges for each person using the testing workspace

Professional lists US$38 per user per month on annual billing. Enterprise adds governance features at US$78. Compare what your team uses before replacing it.

group

A licence for each tester

The published plans charge per user. The annual commitment grows with the licensed team.

fact_check

Case review and approval

Test case versioning, review and approvals sit in Enterprise.

history

Audit records

Enterprise includes audit logs and project administration.

analytics

Reporting across projects

Cross-project reporting is an Enterprise feature.

security

Identity controls

Enterprise includes single sign-on and multi-factor authentication.

backup

Managed recovery and support

Enterprise includes daily backups, configurable restore and priority support.

Your own release records

Give each release a clear evidence trail

Case library

Review the instructions before testing starts

Keep the case, its purpose and its approval together. Your version can follow your team’s own risk and review rules.

  • check Keep requirement and risk references beside each case
  • check Review steps and the expected outcome before approval
  • check Clear approval when the case changes
  • check Keep earlier run instructions intact after a library edit

Release runs

Know what still holds the release

A run keeps the cases as they stood when testing began, with a build, environment and due date.

  • check See passed and unfinished checks together
  • check Hold the run while any defect remains open
  • check Read the original case version behind each result
  • check Combine unfinished work, overdue runs and data reviews in one meeting

Defect follow-up

A passing retest has evidence behind it

Record the failure, name the owner and keep the later result. Closing the issue leaves its history available.

  • check Link each defect to the affected check
  • check Keep earlier failed attempts after a pass
  • check Require a passing retest and resolution before closing
  • check Draft a follow-up for a person to review and send

Owner reports

Read the evidence in your own business format

Prepare release evidence, defect follow-ups and test-data review records with your business name and colours.

  • check Show each run’s remaining checks and open defects
  • check Review stale cases and missing references together
  • check Export your records with their history
  • check Add your own decision rules and reports as the process changes

Make it yours

Design your own TestRail replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from TestRail. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your TestRail replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your TestRail data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real output from the fictional Harbour Portal demo. These are recorded test results, not tests run against a customer system.

forum

Test Management for Claude Code

Connected to your own database

What is holding the current release?

October regression

Build
portal-2026.10-rc1
Environment
staging
Total
3
Passed
1
Remaining
2
Open_defects
1
Decision
hold

Ask it anything

Ten questions to ask your testing records

These questions run against the supplied demo. TestRail also offers reporting and an agent connection. The difference is owning the records and changing the workflow around your business.

chat_bubble Which release has passing checks but unresolved defects?
chat_bubble Which failed checks need a named owner today?
chat_bubble Which cases have not been reviewed for ninety days?
chat_bubble Which case has no recorded requirement or risk reference?
chat_bubble Who has the most unfinished checks?
chat_bubble Which cases failed repeatedly across recorded attempts?
chat_bubble What evidence changed a failed check into a pass?
chat_bubble Which exact case version was included in this release?
chat_bubble Which projects need a test-data retention review?
chat_bubble Who changed a case, and what did the previous version contain?

Switching

How to switch from TestRail

A move usually involves exporting the case library, mapping your fields, checking the import and agreeing separately what historical evidence to bring across.

  1. 1

    Export your case library

    Export the TestRail case library as a one-row-per-case CSV, which the importer expects. TestRail documents a case export, but the exact options can depend on your account, so check with TestRail if you cannot find the right export. Decide separately whether you need historical runs, attachments or linked issue contents, since these need additional mapping.

  2. 2

    Check and load the cases

    The importer checks the whole file before saving. Review the field mapping against the fields and approval rules your team actually uses, then load the cases into a fresh project. Repeat imports are recognised, but do not treat that as a substitute for checking the mapping or confirming which records should be included.

  3. 3

    Review what the import flags

    Review anything the import flags before relying on the imported data. Compare the imported cases with TestRail, paying attention to fields, instructions and approval status. Correct the source data or agree a mapping for exceptions, then check the file again. Make sure you know what was brought across and what was not before your team starts using it.

  4. 4

    Run both systems briefly

    Keep TestRail available while your team uses the new system for a short period. Compare the cases and the work being recorded, including results, evidence and defect follow-ups, and ask users to report anything missing or unclear. Your people and existing test tools still perform the tests. Do not switch off TestRail until you have agreed how to handle history that was not migrated.

  5. 5

    Switch off TestRail

    After your team has checked the new workflow, confirm which historical runs, attachments and linked issue contents must remain accessible. The case library import does not bring all of that history across automatically. Once you have agreed what to keep and where it will live, stop using TestRail for new test management work and arrange any account closure through TestRail.

construction

Where the real effort goes

The work is usually in mapping your case fields and approval rules, deciding which historical runs, attachments and linked issue contents matter, and reconciling anything that does not fit the mapping. This is not a whole-account clone. If you have Enterprise DNA install and run it for you, they handle the migration work with you and agree the scope before you switch.

Not ready for a call?

Get your TestRail switch plan by email

We will send you the step-by-step plan for moving your business off TestRail, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Choose your level of help

Three ways to own your testing system

Open source

Do it yourself

Free and open source

  1. 1 Clone the repo and run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Import a TestRail case CSV into a fresh project and check the mapping
  4. 4 Review the imported cases, create a test run and record real evidence
Get it on GitHub

Built around your business

We customise it

A setup fee for your agreed scope

  • check Your case fields, release rules and approval process
  • check Your TestRail case library brought across, with additional history mapped to an agreed scope
  • check A web front end or different technology if your team needs it
  • check Connections to your existing testing and issue systems, scoped before the build
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your release records connected to the rest of your business
  • check Access controls, backups and operating checks configured for your team
  • check A team to maintain the process and add the next useful report
Book a 30-minute test-tool bill review

Questions

Instead of TestRail, answered

Can we bring our existing TestRail work across? expand_more

The free version imports the case library from a one-row-per-case CSV export. It checks the whole file before saving and recognises repeat imports. Historical runs, attachments and linked issue contents need additional mapping. We agree that migration scope with you before you switch.

Will it run the tests or release our software? expand_more

Your people and existing test tools perform the tests. This system records their results and evidence. Unfinished checks and open defects hold a run. A person makes the release decision, and closing a test run does not deploy anything.

What happens to the old evidence when a case changes? expand_more

Each run keeps the case version used when it began. Later changes clear the case’s approval in the library and leave the earlier run intact. Retests add results, so the original failure stays in the history.

Can our team keep its existing screens and connections? expand_more

Enterprise DNA can build browser forms, reports and connections into your version around how the team tests. We agree what must work first, including team access and recovery, then test that workflow with your people.

What does Enterprise DNA charge, and who owns it? expand_more

The free version is open source. We agree a setup fee for installation, migration and custom work, followed by a retainer when we run it for you. You own your database and your version. Hosting and any external services are agreed as part of the scope.

Bring your TestRail bill to a 30-minute review

Spend 30 minutes with Sam. Bring the number of TestRail seats you pay for, the testing records your team relies on and what holds up a release. We will set the yearly per-seat cost beside owning your version, and map the work involved in bringing your records across.

Book a 30-minute test-tool bill review Get the free version

Test Management for Claude Code is free and open source, published by Enterprise DNA.

Done paying for TestRail?

Book a 30-minute test-tool bill review