Two of the most-requested capabilities in TestRail just shipped together in TestRail 10.2. One accelerates automation for engineering teams, turning test cases into a solid foundation for runnable test scripts in seconds. The other answers a question every QA lead asks before release: which Jira requirements actually have test coverage? Plus, we’ve made your BDD workflows faster and more seamless than ever. Read on to get a look at what’s in store for TestRail 10.2.
AI Test Script Generation: From Test Case to Script Scaffolding in Seconds
If you’ve ever set up automation for a test suite from scratch, you know the drill. Open your IDE. Create a new test file. Import the framework. Set up the browser initialization. Write the setup method. Write the teardown. Structure the test method. Add locators. Write assertions. Add comments for your team.
For every test case. That’s a lot of time, and it adds up fast. AI Test Script Generation is built to take that off your plate.
How it works
Select a test case, choose your framework, and TestRail generates a structured automation script mapped directly to your test steps. From there, a chat-based workflow lets you refine the output until it fits your project—ask it to adjust naming conventions, swap out a locator strategy, or adapt the structure to match your team’s patterns, for example.
The output isn’t just syntactically valid boilerplate. Scripts are generated with clear inline comments tied to each test step, so the logic is readable from day one. Where the generator can’t know your environment specifics, it uses explicit placeholders (like ${PASSWORD}, ${URL}, ${API_KEY}) with inline guidance on exactly what to replace. The structure follows real-world conventions rather than generic scaffolding.
Supported frameworks at launch:
Java:
- Selenium + Maven
- Playwright + Maven
- Cucumber + Selenium + Maven (BDD)
- Cucumber + Playwright + Maven (BDD)
Python:
- Selenium + Poetry
- Playwright + Poetry
- Behave + Selenium + Poetry (BDD)
- Behave + Playwright + Poetry (BDD)
Not yet supported: C#, JavaScript/TypeScript, Ruby, other dependency managers, Cypress, WebDriverIO
If you use a currently unsupported framework, let us know through your beta feedback—that helps us prioritize what comes next!
What You Actually Get
As an example for what to expect, here’s what the AI generates for a login test (Java + Playwright):
java
import com.microsoft.playwright.*;
import org.junit.jupiter.api.*;
import static org.junit.jupiter.api.Assertions.*;
/**
* Test case: Verify invalid password login behavior
* Generated from TestRail test case TC-1234
*/
public class LoginTest {
static Playwright playwright;
static Browser browser;
Page page;
@BeforeAll
static void setupAll() {
playwright = Playwright.create();
browser = playwright.chromium().launch();
}
@BeforeEach
void setup() {
page = browser.newPage();
}
@Test
void testInvalidPasswordLogin() {
// Step 1: Navigate to login page
page.navigate("${LOGIN_URL}");
// Step 2: Enter valid username
page.fill("#email", "${VALID_USERNAME}");
// Step 3: Enter invalid password
page.fill("#password", "WrongPassword");
// Step 4: Click login button
page.click("button[type='submit']");
// Step 5: Verify error message displays
assertTrue(page.isVisible(".error-alert"),
"Error message should be visible");
assertEquals("Invalid credentials",
page.textContent(".error-alert"),
"Error message text should match expected value");
}
@AfterEach
void teardown() {
page.close();
}
@AfterAll
static void teardownAll() {
browser.close();
playwright.close();
}
}Clean, readable, and ready to drop into your project once you swap in the real values.
A note on beta status
AI Test Script Generation is currently a beta feature. The generated scripts are a strong starting point, but they’re not production-ready, and they’re not a replacement for an engineer’s expertise. You’ll still want to review the output, validate locators against your actual UI, and integrate with your existing test infrastructure. Think of it as a fast first draft, not a finished product.
Jira Test Coverage Check: Instantly Identify Test Coverage Gaps
Here’s a scenario most QA teams have lived through. The sprint ends. Coverage metrics look healthy. Then someone asks, “Which stories actually have tests?” …and the honest answer is “We’re not sure.”
The problem isn’t usually negligence, it’s that coverage is hard to see from inside Jira. Stories constantly get linked, moved, and reassigned. A Jira issue can have no test coverage at all and still progress through a sprint without anyone flagging it, because surfacing that gap required manual cross-referencing, which nobody had time to do.
Jira Test Coverage Check fixes that.
How it works
Scope a scan to an Epic, Sprint, or Fix Version, run it on demand, and TestRail instantly identifies which Jira stories, tasks, and requirements have zero test coverage. No exports, no manual comparison, no context switching. Results render directly in TestRail, and you can export a point-in-time snapshot for stakeholders or audit purposes.
The coverage view makes gaps impossible to miss. Instead of a passing aggregate score, you see exactly which issues are untested.
The closed coverage loop
Jira Test Coverage Check doesn’t stand alone: it’s the piece that completes the integration story that started with TestRail 10.
Jira Issue Connect (shipped in TestRail 10) keeps linked Jira issues, their status, and their critical information visible inside TestRail in real time. It answers the question: What’s happening with the issues I’ve already covered?
Jira Test Coverage Check (new in TestRail 10.2) answers the question that comes first: Which issues don’t have any coverage at all?
Together, they close the loop:
- Discover coverage gaps: Coverage Check surfaces untested requirements before they become release risks
- Close the coverage gaps: Link test cases to Jira issues, build out missing coverage
- Keep everything visible: Issue Connect shows Jira status live inside TestRail, so nothing drifts
Full traceability, in one integration. Available for both TestRail Cloud and TestRail Server customers.
Gherkin Syntax Highlighting and a Complete BDD Workflow with Cucumber Parsing
Taken together, this release rounds out something TestRail has been building toward for BDD teams.
Three improvements, one workflow:
TestRail CLI already supports native Cucumber parsing—meaning test results from your Cucumber runs feed back into TestRail automatically, with no custom scripting required. That’s already live for Cloud and Server with the latest version of the TestRail CLI.
With TestRail 10.2, the earlier stages of that workflow get the same treatment. Gherkin scenarios now render with proper syntax highlighting in TestRail: color-coded keywords, monospaced font, preserved indentation—applied automatically to all existing test cases.
And, AI Test Script Generation gives automation engineers a way to go from test case to a runnable Cucumber script in seconds, with built-in chat-based refinement.
The full BDD loop, without leaving your workflow:
- Write or manage your BDD scenarios in TestRail with Gherkin Syntax Highlighting (New in 10.2)
- Generate the automation with AI Test Script Generation (New in 10.2)
- Run it via TR CLI with Cucumber parsing (Live with the latest TR CLI version)
- Get results back via the TR CLI
Get Started with TestRail 10.2
AI Test Script Generation is rolling out now for all TestRail Cloud customers in free open beta, and is switched on by default. It will be available in all TestRail instances by mid-April. Give it a test case and see what it generates!
Jira Test Coverage Check is also available now for both Cloud and Server. Run a scan on your current sprint and find out how much of it is actually covered.
While you’re at it, experience the difference 10.2 and the TR CLI bring to your BDD workflows. Gherkin Syntax Highlighting will apply automatically to all existing test cases and tests, and you can catch up on the latest updates to the TR CLI here.
Want to see TestRail 10.2 in action? Join our live webinar on April 14 to get a first look at AI Test Script Generation and get your questions answered by TestRail experts.
