Large-suite case imports, section deletions, suite moves, and case additions now return before run-statistics recalculation finishes, reducing wait time for release owners managing active test runs.
TestRail 10.7.0 is available on the Early Access track from 11 August 2026 and the default release track from 19 August 2026. The release concentrates on scale, administration safeguards, and automation efficiency, while resolving 12 customer-reported issues.
Faster maintenance for large test suites
Previously, several high-volume case and suite operations waited for TestRail to recalculate run statistics before completing. In a project with many runs, this made routine suite maintenance a scheduling concern rather than a simple content change.
Version 10.7.0 moves that recalculation to a background job. The immediate workflow benefit is faster completion for:
- Bulk test case imports
- Section deletions
- Suite moves
- Test case additions
Multiple changes to the same suite within a short interval are grouped into one recalculation. This reduces duplicate processing and lowers the operational burden during planned test-design updates.
There is an important reporting consideration: passed, failed, and untested counts can briefly reflect the state before a bulk operation. Teams should not treat the immediate post-change view as final evidence for a release gate until the background update has completed.
Reporting controls and release governance
The performance change improves throughput, but it introduces a short consistency window that QA leaders should govern explicitly. Define who can make bulk suite changes near a release decision, how teams confirm that background work has finished, and which report timestamp is accepted as release evidence.
Useful operating controls include:
- Schedule major suite restructuring outside release-gate windows
- Record bulk-change completion times in the release log
- Refresh and verify run statistics before executive reporting
- Separate draft test-design activity from final compliance evidence
Additional performance work speeds milestone-list loading for projects with sub-milestones, retrieval of test-plan entries and runs, project-data loading, and label lookups on test results. These changes matter most where portfolio reporting and test execution run across large project structures.
Safer administration and personal settings
TestRail now warns users when they attempt to leave Administration or My Settings pages with unsaved changes. The prompt appears when navigating away, using browser back or forward controls, or refreshing the page. Closing or refreshing a browser tab invokes the browser's native unsaved-changes dialog.
This addresses a practical control gap. Previously, a newly created API key could appear in the interface yet not persist if the user left before selecting Save. For administrators, that could create failed automation, unplanned rework, and uncertainty over which configuration is actually active.
Platform owners should update administration procedures to require explicit save confirmation for API keys, integration settings, and user-level preferences. It is a small interface change, but it reduces avoidable configuration drift.
More efficient coverage queries through the API
The get_cases and get_bdds endpoints now accept a refs[] array parameter. A workflow that formerly required one request per issue key can retrieve matching cases for multiple references in a single request.
```text
GET /get_cases/{project_id}?refs[]=ENG-101&refs[]=ENG-102&refs[]=ENG-103
```
The existing single-value refs parameter remains supported, so current integrations do not require a change. Teams maintaining sprint coverage dashboards, traceability checks, or work-item synchronization can adopt multi-value filtering when they next revise their API clients.
The operational value is fewer requests, simpler aggregation logic, and less opportunity for partial coverage data when a job processes a set of work items. Validate pagination, authorization, and expected response sizes before promoting the revised query into production automation.
Updated command-line coverage for automation
TestRail CLI is updated to version 1.15.2. The CLI capability set added since version 10.6 includes commands for querying cases, suites, sections, plans, runs, milestones, configurations, statuses, custom fields, tests, users, projects, templates, priorities, and case types.
For DevOps and DevSecOps teams, the practical use is to make test-management data available in controlled scripts and pipeline checks. Examples include checking milestone status before a deployment, collecting run metrics for release evidence, or validating configuration data used by automation.
Treat CLI adoption as an integration change: use scoped credentials, keep command output out of sensitive logs, define ownership for scripts, and test behavior against representative production-scale data.
Reliability fixes that affect enterprise workflows
The 12 fixes target areas that can degrade trust in test evidence or interrupt automated delivery. Notable corrections include:
- Keyword search now finds matching test cases correctly.
- Attachment issues are addressed for upgraded instances, test results, and suite boundaries.
- API-created runs no longer overwrite selections while editing a test plan in the UI.
- The
update_testendpoint no longer returns 403 for Lead-role users updating labels. - Large-run reporting and report generation no longer encounter the identified PHP memory-limit errors.
- Bulk editing more than 100 test cases now maps custom case fields correctly.
- Test cases and overall statistics no longer intermittently disappear from the interface.
Organizations upgrading from earlier versions should give extra attention to attachment retrieval, API response times, and report generation. These are the workflows where a fix can directly affect audit evidence, test visibility, and delivery cadence.
Upgrade priorities
A focused validation plan should cover the release paths that carry the greatest business risk:
- Run a representative bulk import or suite change and confirm eventual statistic updates.
- Test release reporting after the background recalculation completes.
- Create and save an API key or administrative setting, then test navigation-away behavior.
- Compare multi-reference API results against existing single-reference calls.
- Validate attachments, keyword search, bulk edits, large-run reports, and API-created plan runs.
- Confirm CLI scripts and access controls in a non-production environment before rollout.
How Merito helps
Merito helps enterprises assess TestRail upgrades against release governance, automation dependencies, and evidence-retention needs. We can design a risk-based validation pack, review API and CLI integrations, establish reporting controls for asynchronous statistics, and document operational ownership before the default release-track date.
The aim is not simply to install the release. It is to make sure faster maintenance and expanded automation produce dependable release information for engineering leaders, auditors, and delivery teams.
Merito is an authorized TestRail reseller and services partner, listed as a Platinum Verified Partner in the TestRail partner directory. Our TestRail team can scope licensing, sizing, and rollout for 10.7.0, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.