CTAL-TTA practice question 17 of 25

You are an experienced tester on an Agile team that is producing a new application. The product backlog has been refined sufficiently to begin…

You are an experienced tester on an Agile team that is producing a new application. The product backlog has been refined sufficiently to begin development for the first release. This stories in this backlog contain a mixture of functional and non-functional requirements, as well as some technical stories that will provide elements of the application's infrastructure The developers have decided to use TDD as a deveiopment approach but automation of the acceptance tests is not yet planned. You have been asked to recommend whether or not the team should take an atdd approach as well as TDD. what would be the BEST recommendation in these circumstances? SELECT ONE OPTION

Answer options

A: YES. use attd, but for the functional requirements only because it cannot be applied to non- functional or technical requirements.

B: YES. use ATTD for all requirements including non-functional and technical stories. Correct answer

C: NO. do not use ATDD, because it will not work when the acceptance tests are not automated

D: NO. do not use atdd. because it is not compatible with the developers' TDD approach.

Correct Answer:

B. YES. use ATTD for all requirements including non-functional and technical stories.

Explanation

Acceptance Test-Driven Development (ATDD) is a collaborative practice where the whole team defines acceptance criteria as tests before development begins. ATDD is highly versatile and can be applied to all types of requirements, including functional, non-functional, and technical stories. Furthermore, while automating these acceptance tests is a common and recommended Agile practice, automation is not a strict prerequisite for ATDD. The primary value of ATDD lies in the shared understanding, collaboration, and clear definition of "Done" it fosters, which benefits the team even if the tests are initially executed manually.

Why Incorrect

A. ATDD is not restricted to functional requirements; it is equally effective for defining verifiable criteria for non-functional and technical stories.
C. ATDD does not strictly require test automation to be valuable; the collaborative process of defining tests provides significant benefits on its own.
D. ATDD and TDD are highly complementary. ATDD focuses on business-facing acceptance criteria, while TDD focuses on developer-facing unit tests.

References

1. ISTQB Certified Tester Advanced Level - Agile Technical Tester Syllabus (v1.1), Section 2.1: Acceptance Test-Driven Development (ATDD).

2. Adzic, G. (2011). Specification by Example: How Successful Teams Deliver the Right Software. Manning Publications, Chapter 3 (Living Documentation).

Keep practicing

Take the free CTAL-TTA practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test