Marcus UdokangProject Manager| Aivaz ConsultingCalgary, Alberta, Canada
I find these software development techniques complement one another well: Test-Driven Development (TDD), Behaviour-Driven Development (BDD), Acceptance-Test-Driven Development (ATDD). BDD and ATDD are often used interchangeably.
As a product testing methodology BDD allows you to get one behavioural test to pass. Nothing less, nothing more. BDD reflects what real users might actually do. And, it is actually an extension of agile, from conception through to development, testing, marketing, sales, etc. But behavioural tests are slower to run that unit tests. If a BDD test fails it doesn't show the root cause of the problem. Identifying the root cause is a key strength of unit testing. If you say you are agile, does that mean you have to use BDD for app testing?
Would be great to hear your opinion on this issue, and why. Saving Changes...
TDD, BDD and ATDD are just tools. How they are used in the context of an overall set of ways of working can help a team be less or more agile.
When a defect is identified, regardless of the method used to identify it, a quality-focused team will take the time to understand what caused the defect to occur and will use that information as an input into their improvement efforts.
Kiron Saving Changes...
Marcus UdokangProject Manager| Aivaz ConsultingCalgary, Alberta, Canada
