Test Approach and Comparisons between ATDD TDD and BDD

In agile era, all of us are hearing the following approaches. Let’s give insights & compare on three approaches ATDD, TDD and BDD
  • TDD – Test driven development
  • BDD – Behavioral driven development
  • ATDD – Acceptance test driven development
  • EDD – Example driven development
  • Specification by example

Test Approach for ATDD

ATDD usually involves establishing the criteria firstmost often from a user perspective, and, acceptance tests are developed and run to see the results of failure with the right code based on examples.
Customer need technical help. Developer and Tester to provide technical support. Pair wise authoring. Developers need business knowledge. Customer can provide business rules. Pair wise implementation
Test Approach and Comparisons between ATDD TDD and BDD

Test Approach for TDD

TDD is repetition of a very short development cycle. Code is written specifically to pass a given test case. When the written code successfully passes the test (‘green’), the passing code is refactored. Known as ‘red-green-refactor,’ this process is the mantra of TDD.
TDD - Test driven development

Test Approach for BDD

ATDD combines the general techniques and principles of TDD with ideas from domain-driven design ATDD is practice of writing tests first, but focuses on tests which describe behavior, rather than tests which test a unit of implementation.
BDD - Behavioral driven development


Don’t be biased on tools. BDD tools can be used in ATDD and vice versa also. Please focus and understand the practices /process in this blog.
This table will give the ideation on when to use and whom to use these approaches -TDD, ATDD and BDD
Approaches / Comparison ParametersATDDTDDBDD
Users Involved and ScopeCommunication mechanism between Business user, Developer, Tester to ensure requirements are well documentedDeveloper approach between developer and tester to create well written unit of code (module, class, function)Combination of ATDD and TDD.

FocusFocus on capturing requirements in acceptance test and use to drive the development.
Technique to bring the customer in design phase.
TDD is model and paradigm.Focus on behavioral aspect of system for customer and developer but still practice of writing tests.
Bring the customer in testing phase and focus on behavior incrementally to certify.
Agile StepsStep 1: Discuss,
Step 2: Develop,
Step 3: Deliver

It should be repetitive.
Step 1 : Test,
Step 2 : Code ,
Step 3 : Refactor

It should be repetitive.
Build the functionality incrementally guided by expected behavior.

It is the extension of TDD and writing test to fail the feature / behavior
Input documentationAcceptance Criteria + Examples (data and scenarios) = Acceptance TestRequirement documentation will be base for development and testing.Specification document in native language (Plain English) with given, when , then
Acceptance criteria is also specified.
Automation RequiredDoesn’t require automation but needed for regression purposes.Yes. Must haveYes. Must have
Story / Feature : Test  MappingEach story should have acceptance testEach functionality should have implementation of testEach story should have behavior test.
Acceptance criteria and Tests / Target levelAvoid implementation details.
1.       Specific
2.       Measurable
3.       Achievable
4.       Relevant
5.       Time bound
Targeted at Implementation specificBoth of ATDD and TDD
Tools in the market·         Robot Framework,
·         FitNesse,
·         FIT
·         Junit, TestNG, NUnit frameworks,
·         Selenium tool ( any open source tools )
·         MSpec, Specflow – used to define the behavior.
·         Cucumber with Selenium / Serenity
End usersATDD Tests should be readable and focused for customersTDD tests are technical and should be understood by developers/ testersBDD tests should be understandable for both customers and IT team


  1. I read a lot of blog posts and I never heard of a topic like this.

  2. Very very ecxellent work.thank you for giving such very usefull information.

  3. You are providing wonderful information about Test Approach and Comparisons between ATDD TDD and BDD,I got excellent information about blog thank you very much.

  4. I found this article very interesting.

  5. Nice post,Thank you for your informative blog,Great article!

  6. Thanks for your article. It's great to see this post.


Google Q&A Forum