TestRail 10.2.0 Default (1076)

Early Access release track date: 26-Mar-2026

Default release track date: 9-Apr-2026

We’re excited to announce the release of TestRail 10.2.0, introducing new AI-powered automation capabilities, enhanced Jira coverage visibility, improved authentication support, and continued investments in modern testing workflows.

This release focuses on helping teams accelerate automation, improve traceability, and adopt more secure and flexible integrations.

AI Test Script Generation

TestRail now introduces AI Test Script Generation, a new beta feature designed to accelerate script development for automation engineers.

Generate high-quality, well-structured test automation code directly from your test cases through an interactive chat interface.

With AI Test Script Generation, you can:

• Generate structured, well-commented automation code and downloadable project files
• Upload files for additional context (for example existing automation code, selectors, or configuration files) to improve the generated output

• Get clear placeholders and guidance for required setup

• Iteratively refine code through a chat-based interface
• Attach the generated automation to the test case for traceability, reuse, and easy updates as the test case evolves

This is a beta feature and requires manual integration into your automation framework. It represents the first step toward deeper automation assistance in TestRail. 

Jira Coverage Check

TestRail now provides a new way to analyze test coverage across Jira entities, improving visibility into gaps between requirements and testing.

With Jira Coverage Check, you can:

• Evaluate coverage for Jira entities such as Sprints, Fix Versions, and Epics
• Run coverage checks across both the Test Cases Repository and Test Runs
• Identify uncovered items and navigate directly to Jira entities
• Export results via CSV for further analysis

🔐 Passwordless Login Support for Azure

TestRail now supports passwordless authentication for Azure SSO (SAML).

This update removes the previous restriction on authentication methods, allowing TestRail to accept users authenticated by Azure regardless of method (e.g., passwordless, MFA, certificate-based).

This ensures:

• Compatibility with modern Azure authentication methods
• Alignment with Azure as the identity provider
• A more secure and seamless login experience for users

🧪 BDD Syntax Support

BDD scenarios in TestRail now support proper Gherkin syntax rendering, making them easier to read and work with. Keywords such as Given, When, Then, And, and But are clearly formatted with syntax highlighting and structured layout, improving clarity for both manual and automated workflows. Combined with native Cucumber parser support in the TestRail CLI 1.13.3 teams can seamlessly run and report BDD automation end to end.

💻 TestRail CLI 1.13.4

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

• Extended glob support for robot parser for efficient multiple test result file processing
• Added --run-assigned-to-id and --clear-run-assigned-to-id options to add_run command for clearing and setting test run assignees during run creation and updates
• Receive version notifications and use a new update command to easily upgrade to the latest version (v1.13.3).
• Handle multiple test result files with enhanced blob support, improving automation workflows (v1.13.3).

This release also includes the following improvements & fixes:

• Improved - Attachment handling and validation for custom fields
• Fixed - Cannot add empty runs via add_run command due to empty test case validation

API Update:

• update_run: included support for assignedto_id

🐞 Fixes and Improvements (15)

• TR-10585: Test cases marked as deleted still visible after retention period

• TR-12235: Resolved inconsistencies in case_assocs table

• TR-12737: Variable values issues in pop-up

• TR-16765: Added support for Azure passwordless login

• TR-16842: Error when closing test plans resulting in internal server error

• TR-17321: Pasted defect lists in Jira integration not saved correctly

• TR-18487: Data loss when creating or updating test cases

• TR-18623: Data Management export issue

• TR-18640: Jira integration returning 401 error when editing issues

• TR-18662: Column issues on property distribution report

• TR-18671: Project-level permissions not applied correctly

• TR-18785: Scheduled reports not being generated

• TR-18833: Error when importing test cases due to missing estimate field

• TR-19183: Error when opening tests within archived runs

• TR-19290: DateTime error on Admin > Integration Page