4.5.3 Acceptance Test-driven Development (ATDD) Flashcards
ATDD is a t…
test-first approach.
Test cases are created prior to implementing the u…
user story.
The test cases are created by team members with different “p…“, e.g “ “, “d…“ and “ “.
perspectives
customers
developers
testers
Test cases may be executed m…
manually or automated.
The first step is a specification workshop where the u… and (if not yet defined) its a… are “ “, “d…“, and “ “ by the t…
user story
acceptance criteria
analyzed
discussed
written
team members.
Incompleteness, ambiguities, or defects in the u… are resolved d…
user story
during this process.
The next step is to create the t…
test cases.
Test cases can be done by the team a… or by the t…
as a whole
tester individually.
The test cases are based on the a… and can be seen as examples of how the s…
This will help the team implement the u…
acceptance criteria
software works.
user story correctly.
Typically, the first test cases are positive, confirming the c… without “e…“ or e… and comprising the s… executed if everything goes a…
correct behavior
exceptions
error conditions,
sequence of activities
as expected.
After positive test cases are done, the team should perform n…
negative testing.
Finally, the team should cover non-f… (per… , “ “)
non-functional quality characteristics
performance efficiency
usability
Test cases should be expressed in a way that is understandable for the “ “.
stakeholders
Typically, test cases contain sentences in natural language involving the necessary “p…” (if any), the “ “, and the “p…”.
preconditions
inputs
postconditions
The test cases must cover all the characteristics of the u… and should not go b…
user story
beyond the story.
However, the acceptance criteria may detail some of the “ “ described in the u…
In addition, no two test cases should describe the same “ “ of the u…
issues
user story.
characteristics
user story.
When captured in a format supported by a test automation framework, the developers can automate the t… by writing the s…. as they implement the “ “ described by a u…
The acceptance tests then become e…
test cases
supporting code
feature
user story.
executable requirements.