QuestionQ24

Agile software development and Test Techniques

You are an experienced tester on an Agile team developing a new application. The product backlog has been refined enough for development of the first release to begin.

The stories in the backlog include a mix of functional and non-functional requirements, plus some technical stories that will provide parts of the application’s infrastructure.

The developers have chosen TDD as their development approach, but automation of the acceptance tests is not yet planned.

You have been asked to recommend whether the team should adopt ATDD in addition to TDD. What is the BEST recommendation in these circumstances?

Explanation

ATDD complements TDD: it brings stakeholders, testers, and developers together to define concrete acceptance examples that guide implementation, while TDD supports the developers’ lower-level design work. Those acceptance examples are valuable even when they are not automated and can cover functional behavior, quality attributes, and technical or infrastructure requirements. ISTQB guidance notes that automation is not essential to ATDD’s collaborative value and that acceptance criteria should address non-functional as well as functional requirements.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!