Gherkin scenarios, right next to your stories
Write Given, When, Then test cases in Jira, run them by hand or with Cucumber and Behave, and keep every result linked to its story.
Fits the way your team does BDD
BDD starts as a conversation. It shouldn't end in a repo.
Scenario: Valid code lowers the total
Given a guest cart worth $50
When they apply the code SAVE10
Then the order total is $45
# Which story is this? Did it pass?
Scenarios live in code only
Scenarios drift from stories
Results stay in the pipeline
Manual and automated split
Gherkin, managed like any other Jira test
Scenarios get the same plans, executions and reports as every other test in AgileTest.
Gherkin test cases
Generate scenarios with AI
Gherkin preconditions
Run them by hand
Cucumber and Behave results
Trace to requirements
From story to scenario to result
Agree the behaviour
Product, QA and dev describe the rule as Given, When, Then.
Given · When · ThenSave it in Jira
Create a Gherkin test case, or generate one with AI, and link it to the story.
Gherkin test caseRun it your way
Execute it by hand, or automate it with Cucumber or Behave.
Manual · Cucumber · BehaveSee the result on the story
Manual and imported results show up in the same execution and reports.
Executions · ReportsResults land on the right scenario
How Cucumber and Behave reports find their tests in Jira.
"name": "Valid code lowers the total",
"tags": [{ "name": "@SHOP-214" }],
"steps": [{ "result": { "status": "passed" } }]
}, {
"name": "Expired code shows an error",
"tags": [{ "name": "@SHOP-215" }],
"steps": [{ "result": { "status": "failed" } }]
}
Matched by Jira key
Include each test's Jira key in the report and the result lands on that test.
Updates, never duplicates
Cucumber and Behave reports update existing tests instead of creating new ones.
Status from every step
One failed step fails the scenario. Blocked, Retest, Skipped and Query follow in order.
Evidence attached
Screenshots and files embedded in the report are attached to the result.
Plans stay current
Name a Test Plan on import and missing tests are added to it.
Release context included
Tag runs with milestone, environment, revision and Fix Version.
Frequently asked questions
Yes. Gherkin is a built-in test case type, shown as Cucumber, for writing scenarios as Given, When, Then.
Yes. Upload the JSON report or send it through the API, and results attach to the matching Gherkin tests.
Yes. In the AI Generator, set the test case type to Cucumber to generate Given, When, Then scenarios from your requirements.
Yes. Import them from CSV, with the Details column written in Gherkin format.
Yes. Run them in the Execute screen and record Pass or Fail, just like any other test case.
No. Cucumber and Behave reports update existing Gherkin test cases. Include each test’s Jira key in the report, or the import fails.
No. Your framework and pipeline run them. AgileTest manages the scenarios and their results in Jira.
More ways to manage quality in Jira
Put your scenarios where your stories are
Start with one feature. Write the scenarios in Jira, run them, and see every result on the story.