TestRail 10.1.4.1004 Docker Image

Default release track date: 23-Mar-202

We’re excited to announce the release of TestRail 10.1, introducing Smart Archiving for Test Runs and Plans and expanding TestRail’s infrastructure with Data Residency support for new customers.

This release also delivers a significant round of fixes and improvements across reporting, filtering, integrations, and performance, helping teams maintain stable, scalable QA workflows as their usage grows.

Follow the Docker installation instructions here: TestRail 10.1.4 on Docker

Please note that our recommended upgrade path is via TestRail 8.0.4. If you’re still running TestRail 7.0 or below, you should follow the path below:

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');

🌍 Data Residency (New Customers)

TestRail now introduces Data Residency support for new customers, allowing organizations to choose where their data is stored and processed.

Available regions:

  • US - US East (default)
  • EU - Germany
  • APAC - Singapore

When creating a new trial, customers can select their preferred region. All data, including attachments, reports, logs, search indexes, backups, and processing workloads, will remain within the selected geographic location. 

ℹ️ Data Residency is currently available for new customers. Support for existing instances will be introduced in a future release.

🧠 Smart Archiving for Test Runs & Plans

TestRail 10.1 introduces smart closing and archiving controls designed to help teams maintain clean, performant instances as their testing activity grows.

As QA programs scale, large volumes of open and historical Test Runs and Plans can create unnecessary clutter and impact performance. This release introduces new automation capabilities that allow administrators to manage lifecycle events globally.

With automated lifecycle management, admins can:

  • Automatically close inactive Test Runs and Plans after configurable periods
  • Automatically archive closed items to keep projects organized and performant
ℹ️ Smart Archiving is enabled by default to improve your instance performance. If you wish to disable it, please change the options to "Never".
Screenshot 2026-02-13 at 17.33.42.png
Site Settings > User Interface > Automatic Closing/Automatic Archiving

🗂️ Archived Status

A new Archived status clearly marks Test Runs and Plans that have reached the end of their lifecycle. Archived items are:

  • Fully locked and non-editable
  • Excluded from reporting (Print Reports are still available)
  • Still searchable and viewable for historical reference

Teams can continue to reuse past work by creating new runs or plans using the Re-run functionality.

Screenshot 2026-02-13 at 17.38.54.png
Test Runs - Open, completed (closed) and archived

💻 TestRail CLI 1.13.1

The latest version of the TestRail CLI is now available with new capabilities for teams working with BDD workflows, along with performance and maintainability improvements. You can now:

  • Use new commands to work with Gherkin-based test cases and results:

    parse_cucumber
    import_gherkin
    export_gherkin
  • Use the enhanced parse_junit command with the --special-parser bdd option to process BDD scenarios
  • Benefit from centralized logging with structured output and improved configurability
  • Execute tests with multiple case IDs in a single test execution

This release also includes the following improvements:

  • Improved caching to reduce redundant API calls and enhance performance during large executions
  • Internal refactoring to improve stability and maintainability
  • Improved stability when a plan ID is specified and no matching cases are found
👉 Learn more in the TestRail CLI documentation.

🐞 Fixes and Improvements (22)

  • TR-3901: Dynamic Filtering now updates Test Runs and Plans correctly when matching test cases are added or updated
  • TR-5768: Editing a filtered Test Plan no longer removes previously selected filters
  • TR-9929: Reduced unnecessary attachment requests from Shared Steps to improve performance
  • TR-9986: Viewing Test Case history no longer throws undefined property errors
  • TR-11173: Jira Data Center plugin messaging corrected when integration is disabled for specific projects
  • TR-15017: Fixed login issue caused by maximum login attempt limits
  • TR-16257: “Untested” filter now works as expected
  • TR-16266: Test result updates now reflect correctly when changing from Pass to Fail during entry
  • TR-16489: Coverage for References report now respects selected sections
  • TR-16592: “Generate Test Cases” button now enables correctly after activating AI features
  • TR-16640: CSV exports now retain defect values when changing the “Assigned To” field
  • TR-16759: Resolved system log errors on TestRail Server
  • TR-17045: Rich Text fields now retain line breaks correctly
  • TR-17306: Label filtering now works correctly with multiple labels using the “Match Any” option
  • TR-17602: Workload per User bar chart now displays correctly in the Workload Summary report
  • TR-17612: Angle bracket text now renders correctly in Test Case descriptions
  • TR-18302: Fixed an issue where test steps were not visible or editable for some test cases
  • TR-18309: Improved performance and stability when copying or moving items across projects
  • TR-18321: Fixed an issue where test editing was blocked due to unresponsive buttons
  • TR-18369: Resolved incorrect “Test Suite is not a valid test suite” error when searching
  • TR-18681: Resolved undefined array key error when editing test cases
  • TR-18719: Filter option “Match only of the above” now returns correct test cases
  • TR-18760: Error when pushing or referencing a defect

Together, these updates help teams maintain cleaner TestRail instances, support regional data requirements, and improve overall stability across core workflows.

📌 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.
👉 Please check our Cassandra Deprecation documentation.

 

Was this article helpful?
0 out of 0 found this helpful