Key takeaway
- ATDD tools compared: Cucumber, Reqnroll, Robot Framework, Gauge and Serenity BDD, the SpecFlow end of life, a four-step cycle and when to avoid ATDD.
Acceptance Test Driven Development (ATDD) is a practice in which the customer, development and testing perspectives write acceptance tests together before a feature is built. The tests describe the system from the user's point of view, act as requirements, and later confirm the feature works as intended. The tooling is secondary: the Agile Alliance warns that a tool can work against the purpose of ATDD, which is conversation about requirements.
For enterprise teams the useful question is therefore which tool fits the conversation you already have, not which tool is most popular. This guide compares Cucumber, Reqnroll, Robot Framework, Gauge and Serenity BDD, notes that SpecFlow reached end of life, and shows how to adopt ATDD without duplicating our guides to TDD, BDD and ATDD and user acceptance testing.
What is ATDD and how does the cycle work?
According to the Agile Alliance glossary, ATDD brings together customer, development and testing perspectives to write acceptance tests in advance of implementing the functionality. It calls these discussions the "three amigos": the customer asks what problem is being solved, development asks how it might be solved, and testing asks what about the cases nobody has mentioned. The glossary also notes that ATDD is known as Story Test-Driven Development, Specification by Example and Behaviour-Driven Development, names that "exist to stress some differences in approach that lead to similar outcomes".
Teams commonly describe the working cycle in four steps. This is a practical summary, not a standard.
| Step | What happens | Output |
|---|---|---|
| Discuss | The team talks through a user story with the customer and agrees the outcome that matters | Shared understanding and open questions |
| Distil | Requirements become specific acceptance criteria, including edge cases and negative paths | Acceptance tests in agreed wording |
| Develop | Developers implement the feature until the acceptance tests pass, often with unit tests underneath | Passing, automated acceptance tests |
| Demo | The working feature is shown to business stakeholders against the criteria | Feedback, acceptance or refinement |
Automation is optional in the glossary's definition ("sometimes automated"), but automated acceptance tests are what make the criteria a living record that runs on every build.
Which ATDD tool should we choose?
Each description below is taken from the tool's own site, read on 13 November 2026. Confirm current versions, licences and support on each site before you commit.
| Tool | How its site describes it | When it fits |
|---|---|---|
| Cucumber | A tool that supports Behaviour-Driven Development. Plain-text specifications are written in Gherkin (.feature files) and step definitions can be written in many programming languages. Its install page lists official Cucumber-JS, Cucumber-JVM, Cucumber-Ruby, Kotlin, Scala and C++ implementations | Business-readable scenarios shared by product, test and engineering, in a JVM, JavaScript or Ruby stack |
| Reqnroll | An open-source project built from the SpecFlow codebase, described as highly compatible with it and supporting .NET 8.0 and .NET 9.0 | .NET teams that used SpecFlow and need a maintained Gherkin tool |
| Robot Framework | An open source automation framework for test automation and robotic process automation (RPA), with keyword-based syntax and libraries in Python, Java and other languages, supported by the Robot Framework Foundation | Teams that want keyword-driven acceptance tests across web, API and other interfaces |
| Gauge | A free and open source test automation framework whose tests are written in Markdown; it lists JavaScript, C#, Java, Python and Ruby | Teams that prefer specifications as Markdown documents |
| Serenity BDD | Offers living documentation and test reporting that shows which requirements were tested, with the Screenplay pattern and Selenium 4 and RestAssured support; it integrates with Cucumber and JUnit | Teams that need requirement-level reporting on top of an existing BDD runner |
The Agile Alliance glossary also links ATDD with Fit and FitNesse. The same glossary says tools should fit the product owners' needs, not the reverse, so run a one-sprint trial with real stories before you standardise.
What has changed for ATDD tooling?
The main change for .NET teams is the end of SpecFlow. The Reqnroll project states that SpecFlow reached end of life on 31 December 2024, that its GitHub projects were deleted on 1 January, and that it will not be updated for newer .NET platforms. Reqnroll calls migration "fairly straightforward, but it is not effortless", and says projects with async or parallel execution, custom dependency injection or third-party plugins may need extra help.
A second change is the use of AI coding assistants to draft scenarios and step definitions. That speeds up typing, not agreement. Treat generated scenarios as proposals: the three amigos still own the acceptance criteria, and a failing test must never be "fixed" by an agent editing the test to match the code.
How is ATDD different from other kinds of testing?
ATDD sits above unit testing and beside user acceptance testing. Use the guides below for the neighbouring practices rather than repeating them here.
| Practice | Question it answers | Read more |
|---|---|---|
| Unit testing | Does each small piece of code behave correctly? | Unit testing guide |
| TDD, BDD and ATDD | Who writes which test, and at what level? | TDD vs BDD vs ATDD and TDD guide |
| ATDD (this guide) | Have we agreed what "done" means before building, and is it checked automatically? | Tool choice and adoption below |
| API testing | Do service interfaces meet their contracts? | API testing guide |
| Regression testing | Did a change break behaviour that worked before? | Regression testing guide |
| Functional and non-functional testing | Does it do the right thing, and how well? | Functional vs non-functional |
| User acceptance testing | Do business users accept the finished system? | UAT guide |
ATDD also supports shift-left testing, because ambiguity is found in the Discuss and Distil steps instead of in late-cycle rework.
How do we adopt ATDD in an enterprise team?
- Pick one product area with frequent requirement disputes, not the whole portfolio.
- Name the three perspectives for each story: a business owner, a developer and a tester.
- Write acceptance criteria as examples in plain language before development starts.
- Choose one tool with a one-sprint trial, using the table above and your language stack.
- Automate the criteria at the service or API level where you can, because the Agile Alliance notes that testing through the full user interface is less effective.
- Run the acceptance suite in the build pipeline and show results to the business owner in the Demo step.
- Review the suite each release: retire scenarios nobody reads and fix those that fail for the wrong reason.
What about governance, security and cost?
| Area | What to decide |
|---|---|
| Ownership | Business owners own the criteria; engineers own the step definitions. Both are reviewed like code. |
| Traceability | Link each scenario to a story or requirement so auditors can see what was agreed and what was tested. |
| Test data | Use synthetic or masked data in acceptance environments; keep secrets out of feature files. |
| Maintenance cost | Scenarios coupled to the user interface break often. Prefer service-level steps and keep scenarios short. |
| AI-generated tests | Require human review of generated criteria and record who approved them. |
If agents help generate or run acceptance checks, AgentQA offers automated quality assurance for AI, and ElixirClaw is an agentic OS platform to build, orchestrate and govern AI agents and automation workflows while keeping humans in control. Both descriptions come from their own sites.
When is ATDD the wrong choice?
- There is no business owner available to join the Discuss step. Without that conversation, ATDD becomes test scripting.
- The work is a small technical change with no user-visible behaviour; unit tests cover it better.
- The team would automate every scenario through the user interface, which the Agile Alliance describes as less effective.
- A tool is chosen first and the process fitted around it, which the glossary warns against.
To map one release decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.
Frequently asked questions
What is acceptance test driven development in simple terms?
It is a practice where customer, development and testing perspectives write acceptance tests together before a feature is built, so everyone agrees what done means and the tests later confirm it.
Which ATDD tool is best?
There is no single best tool. Cucumber and Reqnroll use Gherkin, Robot Framework is keyword-based, Gauge uses Markdown specifications and Serenity BDD adds requirement-level reporting. Choose by language stack and how your business owners prefer to read specifications.
Is SpecFlow still supported?
No. The Reqnroll project states that SpecFlow reached end of life on 31 December 2024 and will not be updated for newer .NET platforms. Reqnroll, built from its codebase, is the maintained alternative.
What is the difference between ATDD and BDD?
The Agile Alliance notes the terms exist to stress differences in approach that lead to similar outcomes. ATDD stresses acceptance tests agreed in advance; BDD stresses shared behaviour examples and is closely tied to Gherkin tools.
Does ATDD replace user acceptance testing?
No. ATDD defines and automates acceptance criteria during development. User acceptance testing is the final confirmation by business users that the finished system meets their needs.
Should acceptance tests go through the user interface?
Prefer service or API level where possible. The Agile Alliance says testing through the full user interface is less effective, so ATDD favours interfaces built for functional testing.
Explore the XenonStack platform family: ElixirData · ElixirClaw · ElixirHub · NexaStack · MetaSecure · Neural AI · AgentGRC · AgentSRE · AgentAnalyst · AgentInstruct · AgentRAI · AgentScrum · AgentSearch · AgentForce · AI Aviator · SAIF Aviator · CohortIQ · XenonStack AI · XenonStack UAE
