TestRail 10.7.1.1003 Docker Image

Default release track date: 2-Sep-2026

TestRail 10.7.1 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
• Bulk case imports, section and suite operations, and case additions complete more quickly for large projects
• Multiple changes to the same suite within a short window are batched into a single recalculation
• Run statistics (passed, failed, untested counts) are updated shortly after the operation via a background job

ℹ️ Run statistics may briefly reflect the state prior to a bulk operation until the background job processes all the updates.

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. 

Additional improvements in 10.7.1 include

• Faster milestone list loading for projects with sub-milestones
• Improved performance when retrieving test plan entries and runs
• Reduced query overhead when loading project data
• Faster label lookups when loading test results

🔔 Unsaved Changes Protection

TestRail 10.7 adds an unsaved changes warning to Administration and My Settings pages. Previously, navigating away from these pages without clicking Save would discard changes without any warning — including newly created API keys, which appeared in the UI but were not persisted until the page was explicitly saved.

Now, if you attempt to navigate away, use browser back/forward navigation, or refresh the page with unsaved changes, TestRail displays a confirmation prompt to save or discard before leaving. Closing or refreshing the browser tab triggers the browser's native unsaved changes dialog.
 

🔌 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.

The get_cases and get_bdds endpoints now support a refs[] array parameter, allowing you to filter by multiple reference IDs in a single API call.

Previously, checking test coverage across a sprint required one API call per issue key. With refs[] syntax, all matching test cases are returned in one request:

GET /get_cases/{project_id}?refs[]=ENG-101&refs[]=ENG-102&refs[]=ENG-103

The existing ?refs= single-value parameter is unchanged - all existing integrations continue to work without modification.

💻 TestRail CLI 1.15.2

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

• cases, suites, section: query test cases, suites, and sections with pagination and JSON output
• plans and plans add: retrieve test plans and create plans with entries, milestones, and dates
• runs: get and list standalone test runs with status and result metrics
• milestones: query project milestones, due dates, and completion status
• configurations: list configuration groups and configs across a project
• statuses: list result statuses and case statuses (Enterprise 7.3+)
• casefields, resultfields: query custom case and result fields with project filtering
• tests:  query test instances within a run
• users: get users by ID, email, or list all
• projects: query project details or list all projects
• templates: query available field layout templates
• priorities, casetypes:  list test case priorities and types

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 (27)

• 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"
• TR-21431: Fixed custom fields behavior when editing it's configuration
• TR-13809: Fixed keyword search not finding matching test cases
• TR-18737: Fixed test case description displaying scrambled text and overlapping the page header
• TR-19607: Fixed API-created test runs incorrectly overwriting run selections when editing a test plan in the UI
• TR-20057: Fixed section dropdown search in AI Test Case Generator not filtering results
• TR-20295: Fixed attachment-related issues for instances upgraded from earlier versions
• TR-20346: Fixed test cases occasionally missing from the UI and overall test statistics
• TR-20349: Fixed attachments not displaying in test results following a previous database migration
• TR-20364: Fixed bulk edit for 100+ test cases not displaying correct custom case field mappings
• TR-20372: Fixed update_test API endpoint returning a 403 error for users with the Lead role when updating labels
• TR-20382: Fixed attachments from one test suite incorrectly appearing in a different suite
• TR-20514: Fixed API performance degradation affecting instances upgraded from earlier versions
• TR-20609: Fixed PHP memory limit errors when generating reports or opening large test runs

📌 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.