TestRail 10.6.1.1001 Server

Default release track date: 23-Jul-2026

TestRail 10.6 is built for enterprise scale. This release delivers significant performance improvements for large test suites, expands the TestRail API and CLI, and includes a broad set of fixes across test management, PDF reporting, and integrations.

Once the upgrade is complete, you must open _config/config.php in your Docker files folder, and add new line with: 

define('TR_CHROME_PATH', '/usr/bin/chrome-headless-shell-linux64/chrome-headless-shell');

⚡ Performance & Scalability

10.6 delivers measurable improvements that make TestRail faster and more reliable at enterprise scale.

Faster day-to-day work

• Test case pages load ~80% faster for AI-enabled projects containing more than 11,000 test cases. 
• API requests against archived runs with many custom fields are 35-50% faster. 

Additional improvements:

• Faster plan creation and updates through reduced database contention
• More responsive test run and plan creation on large projects
• Faster large-scale update operations
• More efficient addition and removal of cases from runs

Better scalability for enterprise instances

• Run creation now succeeds reliably for projects containing 25-28 million tests, eliminating previous out-of-memory failures.
• Bulk assignment operations on runs with more than 30,000 tests now complete reliably without timing out or failing.
• PDF reports now generate successfully for test plans with 1,000+ runs, resolving previous failures on enterprise-scale projects. 

🔌 API Enhancements

New get_version endpoint 

A new GET /index.php?/api/v2/get_version endpoint returns the current TestRail version—for example, {"version": "10.6.0.1041"}. Useful for automation tools and integrations that need to determine which TestRail version they're working with. Requires an active, authenticated session.

System fields now returned by get_case_fields and get_result_fields 

Previously, both endpoints returned only custom fields. They now return system fields alongside custom fields, with each field including an is_system boolean. This allows automation tools to fully introspect field definitions and determine which template a given system field belongs to.

💻 TestRail CLI 1.15.1

TR CLI 1.15.1 adds six new read-only query commands for test execution data, project configuration, and field introspection:

• runs · milestones · configurations · statuses · casefields · resultfields

All commands support pagination (--offset, --limit), JSON output, and flexible project specification—consistent with the cases, suites, sections, and plans commands introduced in 1.15.0.

🐞 Fixes and Improvements (14)

• TR-12238: Milestone and test case print reports no longer hang indefinitely on large datasets
• TR-12409: Fixed an issue with the TestRail/Jira integration
• TR-16695: Deleting a large number of orphaned attachments no longer returns an error
• TR-16804: PDF reports no longer hang on large test runs, plans, and milestones
• TR-19752: Fixed an issue where test cases could appear missing from a project
• TR-19753: Test case content now renders correctly after API updates involving custom fields
• TR-19762: Fixed a data migration issue from version 10.1 that could cause test cases to be incorrectly moved or deleted
• TR-20182: Dashboard and Project Activity Charts are now displaying correctly
• TR-20217: Adding a new build no longer shows an unexpected confirmation message
• TR-20260: Editing test cases and adding new test cases with steps now saves correctly
• TR-20275: Property Distribution reports for cases and results now generate successfully
• TR-20296: Jira custom fields no longer disappear after adding a personal integration
• TR-20347: Fixed performance degradation when creating test runs and test plan entries
• TR-20561: Fixed an error in certain API operations caused by a missing expected value
• TR-20888: Test runs are failing to load and returning an "Undefined variable: $test_count' error"

📌 Cassandra Deprecation Enforcement

Starting with TestRail 9.5 Server, Cassandra is officially deprecated and enforcement is in place.

• Admins must first run the Cassandra deprecation script in version 9.4.1 before upgrading to 9.5.
• If the script has not been executed, the upgrade to 9.5 will be blocked and a  warning message will be displayed  during the upgrade process.