TestRail 10.5.0 Default (1038)

Early Access release track date: 17-Jun-2026

Default release track date: 29-Jun-2026

We're excited to announce TestRail 10.5, introducing AI-powered test prioritization, expanded API capabilities for teams who automate at scale, and a set of fixes that improve overall quality of the platform.

❖ SparkleIconSembi.pngAI-Powered Test Prioritization

QA teams often face the same problem before a release: there are more tests available than time to execute them all. As regression suites grow and release cycles accelerate, it becomes harder to identify which tests matter most for the current release.

Prioritise with AI helps solve this by automatically ranking tests inside a test run based on likely risk, historical failures, linked defects, execution patterns, and semantic analysis of test case content. Teams can also guide the AI using labels and natural-language instructions focused on recent changes, high-risk areas, or business-critical workflows.

TestRail - 10.5 Release Graphics (Final w Sembi IQ)_UI .png

This helps teams:

  • Focus testing effort on the highest-risk areas
  • Reduce release risk during time-constrained cycles
  • Accelerate regression testing
  • Improve confidence before release

Prioritise with AI is available for TestRail Cloud only.

⚙️ More from Every API Call

Your CI pipeline doesn't care about test case IDs. It cares about coverage: which requirements have tests, which tests are tagged for this run, which ones failed. In 10.5, the TestRail API closes the gap between the data you have and the answers your integrations need.

Key capabilities:

  • Case titles in test and result responses: get_tests and get_results_for_run now include case_title directly, so you can display human-readable results without additional case lookups
  • Filter cases by label or external reference: get_cases now accepts label_id and refs as filter parameters, so you can retrieve exactly the cases tagged for your scope or linked to a specific Jira ticket, requirement ID, or story
  • Bulk BDD content retrieval: the new get_bdds endpoint returns Gherkin feature content for multiple cases at once, with support for label, suite, section, and refs filtering
  • New label management APIs: create, read, update, and delete labels programmatically, with bulk add and bulk update operations supported

Additional improvements:

  • Bulk case title resolution: the new get_case_titles endpoint maps a list of case IDs to their titles in a single lightweight call
  • Plan membership in run responses: get_runs now includes plan_id, so you can tell whether a run belongs to a test plan without a separate lookup
ℹ️ The case_title and plan_id fields are additive and backward-compatible. If your integration uses strict-schema auto-generated clients (e.g., OpenAPI-generated SDKs that reject unknown properties), review your response models after upgrading.

💻 TestRail CLI 1.15.0

The latest version of the TestRail CLI is now available with new capabilities. Now you have:

  • New read-only data query commands:  casessuitessections, and plans each include get and list subcommands, giving automation tools and AI-native workflows direct access to TestRail data
  • All query commands support pagination (--offset--limit), JSON output (--json-output), detailed field view (--show-all-fields), and flexible project specification
  • New results command for listing or updating existing test results, with pagination and JSON output support (requires TestRail 10.4 or later)
  • Optimized attachment uploading with improved progress tracking
  • Fixed an issue where large attachment uploads could fail with an "unable to find result_id" error
👉 Learn more in the TestRail CLI documentation.

🐞 Fixes and Improvements (21)

  • TR-10690: Updating a test case's suite via the API now saves correctly
  • TR-11670: Printing a milestone no longer returns a server error
  • TR-11976: Resolved an issue where certain reports took an excessive amount of time to generate
  • TR-12410: Exporting test cases as CSV no longer fails with a server error
  • TR-12455: Updating a run within a plan entry via the API now works correctly
  • TR-12791: Resolved a performance issue with milestone queries that could affect instance responsiveness
  • TR-16241: Printing test plans and suites no longer returns a server error
  • TR-16344: Exporting test cases and tests to Excel now works correctly
  • TR-16472: Fixed an issue where completed test runs could show missing test cases after upgrading from an older version
  • TR-16750: Attachments uploaded before January 2025 now display the correct project association
  • TR-17208: Resolved a data discrepancy where API results could differ from what was shown in the TestRail UI
  • TR-17247: Sub-section sort order no longer resets to default when a parent section is reordered
  • TR-17260: Pasting code-formatted text into comment fields now works correctly
  • TR-18873: Labels are now correctly imported when importing test cases from CSV
  • TR-19432: API responses no longer incorrectly encode < and > characters as HTML entities
  • TR-19476: Resolved intermittent errors that could occur during certain integration workflows
  • TR-19517: CSV imports no longer create duplicate sections
  • TR-19562: Resolved a performance issue that could affect some test plans
  • TR-19794: Adding configuration-based runs to an existing plan entry via the API now works correctly
  • TR-19797: AI test case generation no longer fails with a service unavailable error
  • TR-19928: Clicking "+ Add Test Run" multiple times no longer creates duplicate test runs
Was this article helpful?
0 out of 0 found this helpful