Education & Training

Services & Support



{{search ? 'Close':'Search'}}

Test-Driven Development

Your Quick Guide to Test-Driven Development (TDD), Behavior-Driven Development (BDD) and Acceptance Test-Driven Development (ATDD)

Need to know about TDD, BDD and ATDD?
You’ve come to the right place.

Test-driven development, behavior-driven development and acceptance test-driven development do have a few differences, but they all share the same overlying objective–they all help deliver better quality software, quicker.

  • “Is this code correct?” is the driving question behind test-driven development.
  • “Is this what we should be testing?” is the question that behavior-driven development seeks to answer.
  • “Is the code doing what it is supposed to do?” is the primary question behind acceptance test-driven development.

Demystifying Test-Driven Development vs. Behavior-Driven Development vs. Acceptance Test-Driven Development

This blog explores what test-driven development, behavior driven development  and acceptance test-driven development are all about. How do they work? How are they different? And what are their effects on the development and testing process? 

How to Get the Gains (Not the Pains) of Behavior Driven Development 

Behavior-driven development is more commonly known for its use of the “given-when-then” format to defining each user story, facilitating clear alignment of a user story to a desired business outcome. But behavior-driven development has had its ups and downs over the years. But what if you can implement the principles of behavior-driven development, dealing with the overhead that comes with traditional behavior-driven development?

Read this blog to learn how visual behavior-driven development  can help you realize all the benefits of  behavior-driven development, while squashing all the dreadful maintenance overhead the usually comes with it.

Test Design Automation Reference Guide

As more and more organizations adopt test-driven, agile development methods, they gravitate towards test design automation—practices and technology that help test teams automatically generate reusable test assets like test cases, test data and test automation scripts right from clearly defined and complete requirements. In the end, test automation and development within the same sprint becomes a reality.

Download this Reference Guide to learn how to apply in-sprint test automation practices, explore the many benefits of test design automation and find real-world use cases.

Start Your CA Agile Requirements Designer Trial Today

Application quality is routinely compromised by poorly defined requirements and slow, unsystematic testing. Many times, defects go undetected, leading to late rework, project delays and ultimately a poor user experience.

CA Agile Requirements Designer helps simplify the application of agile in-sprint test automation practices throughout new or existing software development lifecycles. You can automatically create optimal test cases and test automation scripts right from your clearly defined requirements. 

Sign up today and be on your way to a 30-day trial.

Get in touch with CA.