TestRail 10.6.0 makes test run creation reliable for projects containing 25–28 million tests, removing prior out-of-memory failures that could delay release decisions for the largest portfolios.
Performance gains where scale creates delivery risk
Large test inventories can turn routine quality-management tasks into queueing, timeouts, and incomplete evidence. This release targets those operational constraints across test case browsing, run creation, bulk assignment, archived-run API activity, and PDF reporting.
Measured and corrected improvements include:
- Test case pages load about 80% faster for AI-enabled projects with more than 11,000 test cases.
- API requests against archived runs with many custom fields are 35–50% faster.
- Test plan creation and updates reduce database contention.
- Adding and removing cases from large runs is more efficient.
- Bulk assignment on runs exceeding 30,000 tests completes without previous timeout or failure patterns.
- PDF reports generate successfully for plans containing more than 1,000 runs.
For release owners, these changes matter because test evidence is often needed at a fixed decision point: a change advisory review, a deployment gate, or an audit request. Faster work is useful; reliable completion under peak data volumes is the more important control.
Cloud custom field indexing supports faster queries
TestRail Cloud administrators can now index up to five custom case fields. Available field types are Checkbox, Date, Dropdown, Integer, Milestone, and User. The setting is managed in Admin → Customization → Case Fields through the Enable Indexing option, and indexed fields display an index icon.
This is a practical option for organizations that routinely filter or report by fields such as product area, risk classification, accountable owner, milestone, or compliance category. It can reduce waiting time for views that guide triage and release reporting.
Indexing should be governed rather than applied broadly:
- Identify fields used most often in filters and reports.
- Confirm that field definitions are standardized across teams.
- Limit indexing to evidence-producing workflows with measurable query delays.
- Account for additional storage use and a possible small write-performance impact.
- Review indexed fields after taxonomy or reporting changes.
That trade-off need review by platform owners. The five-field limit also encourages a clear prioritization decision instead of uncontrolled performance tuning.
API and CLI changes improve automation inspection
The API now provides GET /index.php?/api/v2/get_version, returning the connected TestRail version, such as {"version":"10.6.0.1041"}. Automation can use this to detect platform capabilities before running version-dependent logic. The endpoint requires an active authenticated session.
The get_case_fields and get_result_fields endpoints now return system fields alongside custom fields. Each field includes an is_system flag, allowing integrations to distinguish platform-defined and organization-defined metadata and identify the relevant system-field template.
TestRail CLI 1.15.1 adds six read-only commands:
runsmilestonesconfigurationsstatusescasefieldsresultfields
These commands support --offset, --limit, JSON output, and flexible project specification. For DevOps teams, that broadens the ability to inventory execution data and configuration through controlled scripts rather than manual exports.
Governance and workflow implications
The API and CLI additions make test-management metadata more observable, but they also create a reason to review automation ownership. Teams should define which service accounts may read project configuration and execution data, how credentials are rotated, and where exported JSON is retained.
Recommended implementation actions include:
- Add version checks to shared integration libraries where behavior differs by release.
- Validate API client parsing against system and custom fields together.
- Test CLI pagination on representative large projects before placing queries in scheduled jobs.
- Record indexed custom fields and their business purpose in the test-management operating model.
- Establish performance baselines for high-volume runs, reports, and release dashboards.
These steps support repeatable evidence collection without creating unowned scripts or inconsistent metadata rules across delivery groups.
Reliability fixes reduce reporting and integration exceptions
TestRail 10.6.0 includes 14 fixes across workflows that can affect release confidence. Notable corrections include PDF and print reports hanging on large datasets, property distribution reports failing to generate, test cases appearing missing, and test case content rendering incorrectly after custom-field API updates.
The release also addresses a migration issue from version 10.1 that could incorrectly move or delete test cases. Jira-related fixes cover an integration issue and custom fields disappearing after a personal integration is added. Other corrections improve dashboard and project activity charts, test-case saving with steps, attachment cleanup, build creation, test-run and plan-entry creation, and certain API operations.
For regulated or high-assurance teams, these fixes warrant focused regression checks after upgrade. Validate the reports used as approval evidence, the Jira fields used for traceability, and any migration history or archive workflows that matter to audit records.
How Merito helps
Merito helps enterprises assess TestRail 10.6.0 against actual portfolio scale, integration dependencies, and control requirements. We can define an upgrade test plan, select the right Cloud fields for indexing, validate API and CLI automation, and produce post-release evidence for governance stakeholders.
The goal is not just to install the release. It is to confirm that performance, reporting, access controls, and delivery workflows behave as intended under your operating conditions.
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.6.0, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.