TestRail 10.3.1 Default (1009)

Early Access release track date: 23-Apr-2026

Default release track date: 11-Mar-2026

We’re excited to announce the release of TestRail 10.3.0, bringing one of our most requested usability updates, new capabilities for AI testing, and a significant investment in platform quality.

🌙 Dark Mode & High Contrast

Dark Mode is back in TestRail! 

Alongside it, we’re introducing High Contrast mode, designed to improve accessibility and readability across different environments.

With theme support, you can now:

• Reduce eye strain during extended sessions
• Improve visibility in low-light or high-glare conditions
• Choose a display mode that fits your workflow and preferences

Learn how to configure it here.

AI Evaluation Template with Quality Insights Dashboard

Testing is evolving. As systems become more dynamic and AI-driven, outcomes are no longer always predictable, and traditional pass or fail simply isn’t enough.

That’s why the AI Evaluation template is now available in TestRail.

It introduces a structured way to test systems where results can vary between executions, giving teams the ability to evaluate quality across multiple dimensions rather than relying on a binary outcome. While it’s designed with AI-powered features in mind, it also supports any scenario where understanding how well something performs is just as important as whether it works.

Best of all, it fits seamlessly into the way you already work. Your existing TestRail workflows and API integrations remain unchanged, so you can start adopting this new approach to quality without disruption.

For AI-driven use cases, the template helps teams to:

• Evaluate AI-generated outputs such as chatbot responses or recommendations
• Assess behaviour that varies between executions
• Measure quality across dimensions like accuracy, relevance, and safety

To support this, the Quality Insights dashboard provides a clear view of evaluation results, helping teams to pinpoint problematic areas in complex systems, make more data-driven go or no-go release decisions, and compare performance across models to choose the right LLM for their features.

For non-AI scenarios, the Quality Rating result field can also be reused with other templates to evaluate:

• Performance, such as perceived responsiveness or behaviour under load
• Security and compliance, including prompt injection resistance or data leakage
• Any system where quality cannot be reduced to a binary result

Improved Generate Test Cases with AI

We’ve improved Generate Test Cases with AI to give you more control over your outputs.

You can now define the maximum number of test cases the AI should generate, helping you tailor results to your specific needs. Whether you’re looking for a focused set of high-impact tests or broader coverage, this ensures the output stays relevant, manageable, and aligned with your workflow.

🧩 Quality Improvements

TestRail 10.3 includes a significant set of fixes and improvements, representing a focused investment in platform stability and reliability.

These updates improve consistency and performance across core workflows, helping teams operate more smoothly as their usage scales.

💻 TestRail CLI 1.14.1

The latest version of the TestRail CLI is now available with new capabilities. You can now:

• Preserve Markdown syntax when sending content to TestRail using the new WYSIWYG editor (requires TestRail 10.3.0 or higher)
• Use the enhanced parse_junit command with the --special-parser multisuite option to create or update a single test plan with one run per suite from a JUnit XML report
• Update runs using the enhanced add_run command, including options to clear attributes such as description, dates, milestone, and case selection

This release also includes the following improvements & fixes:

• Improved attachment handling when parsing multiple reports, ensuring attachments are correctly associated with their respective resultsFixed attachment upload failures when adding results to empty test runsImproved run updates to ensure case selection is applied correctly

🐞 Fixes and Improvements (72)

This release includes more than 72 fixes and improvements across the platform, addressing issues related to:

• Reporting performance and accuracy
• Jira integrations and workflows
• Data handling and stability
• UI consistency and usability

List of fixed tickets:

• TR-11789: Error message shown when navigating away from a page

• TR-13277: Increased PHP memory limit for Docker deployments

• TR-13458: Milestone field not displayed in test case version history

• TR-13553: Status not shown when selecting test cases for a test run

• TR-14014: Data sets not creating multiple test runs in multi-suite projects

• TR-14099: Unable to edit case fields

• TR-14429: Custom field values not imported via XML

• TR-14592: Test runs displayed in incorrect order within test plans

• TR-14677: Incorrect tester and filtering in Test Run Summary report

• TR-14819: Test labels editable in closed runs and plans

• TR-14902: Attachments deleted in test cases with steps

• TR-15108: Incorrect attachment ID returned by get_section endpoint

• TR-15574: Unable to bulk update references

• TR-15593: Bulk editing users across all projects not displaying correctly

• TR-15594: Incorrect case count in plans created with dynamic filters

• TR-15624: Jira Test Management app returning 403 error

• TR-15725: Unable to delete test runs

• TR-15785: Jira plugin appearing in projects where it should not

• TR-15913: Test case status not displayed correctly in reports

• TR-16037: Reports generated without data

• TR-16176: Dynamic filter mismatch in test runs with manual section selection

• TR-16222: Webhook %event_creator% returning incorrect user

• TR-16240: “Edit all” filter causing undefined variable error

• TR-16288: Attachment filtering not working in Data Management

• TR-16383: Error when deleting attachments from closed runs

• TR-16500: Ignored status still appearing in Jira integration reports

• TR-16580: Jira push defect fields not matching project configuration

• TR-16596: Filtering with underscore characters not working in shared steps

• TR-16605: Unable to delete projects due to memory errors

• TR-16663: Offline error shown when generating AI test cases

• TR-16677: Error when deleting attachments after v9.4

• TR-16736: Error when assigning users

• TR-16823: Permission error in cross-project reports

• TR-16943: Enter key not creating line breaks in BDD scenarios

• TR-16948: Long text truncated in results fields

• TR-17009: Editing section title removes description

• TR-17071: Case references in preconditions not rendered as links

• TR-17089: API stability improvements

• TR-17117: Markdown and code block formatting issues

• TR-17119: Blank exports when exporting test runs

• TR-17133: HTML tags appearing in CSV/Excel exports

• TR-17136: Missing spacing in H2 headings in descriptions

• TR-17149: Admin overview banner display issues

• TR-17204: Error when deleting a project

• TR-17209: Error when hovering over references or defects

• TR-17232: Unable to add references using the Add button

• TR-17457: Editing section title removes description

• TR-17627: Unable to save test cases

• TR-18435: Incorrect “Tested By” and “Tested On” values in test runs

• TR-18468: Missing TestRail panel in Jira projects

• TR-18479: Defect ID not included in Excel exports

• TR-18547: Angle bracket characters not visible in test fields

• TR-18608: HTML tags added to test cases unexpectedly

• TR-18891: Custom result fields not retaining values

• TR-18945: Dynamic filter configuration not visible in edit mode

• TR-18958: Error when uploading .feature files

• TR-19018: Custom field values not removed from database when cleared

• TR-19048: API error when adding cases (500 Internal Server Error)

• TR-19071: Incorrect defect shown in run defect column

• TR-19175: “Assign To” field mismatch between cache and submission

• TR-19202: Jira references not fetched, causing data loss on save

• TR-19224: Special characters displayed incorrectly after upgrade

• TR-19233: Custom result field updates not reflected in test runs

• TR-19254: Missing sorting option in Test Run view

• TR-19337: Test runs not appearing in search results

• TR-19365: Navigation issue when selecting test cases across pages

• TR-19381: get_test API failing for archived runs

• TR-19424: Jira data sync and OAuth integration failures

• TR-19431: Markdown syntax preserved in API responses

• TR-19480: Test case order not preserved after CSV import

• TR-19640: Error when editing more than 50 test cases

• TR-19790: Fixed an issue where tests were not shown after switching to compact view from the second page of Test Runs & Results

• TR-19874: Fixed migration failures when adding AI evaluation fields for instances with many custom fields