Page "Acceptance testing" Paragraph 18
from
Wikipedia
The customer specifies scenarios to test when a user story has been correctly implemented.
A story can have one or many acceptance tests, whatever it takes to ensure the functionality works.
Acceptance tests are black box system tests.
Each acceptance test represents some expected result from the system.
Customers are responsible for verifying the correctness of the acceptance tests and reviewing test scores to decide which failed tests are of highest priority.
Acceptance tests are also used as regression tests prior to a production release.
A user story is not considered complete until it has passed its acceptance tests.
This means that new acceptance tests must be created for each iteration or the development team will report zero progress.
Page 1 of 1.
2.540 seconds.