Acceptance Testing in Extreme Programming
Acceptance testing is a term used in agile software development methodologies, particularly Extreme Programming, referring to the functional testing of a user story by the software development team during the implementation phase.
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.
Read more about this topic: Acceptance Testing
Famous quotes containing the words acceptance, testing, extreme and/or programming:
“To be conservative requires no brains whatsoever. Cabbages, cows and conifers are conservatives, and are so stupid they don’t even know it. All that is basically required is acceptance of what exists.”
—Colin Welch (b. 1924)
“Traditional scientific method has always been at the very best 20-20 hindsight. It’s good for seeing where you’ve been. It’s good for testing the truth of what you think you know, but it can’t tell you where you ought to go.”
—Robert M. Pirsig (b. 1928)
“When raging love with extreme pain
Most cruelly distrains my heart,
When that my tears, as floods of rain,
Bear witness of my woeful smart;
When sighs have wasted so my breath
That I lie at the point of death,”
—Henry Howard, Earl Of Surrey (1517?–1547)
“If there is a price to pay for the privilege of spending the early years of child rearing in the driver’s seat, it is our reluctance, our inability, to tolerate being demoted to the backseat. Spurred by our success in programming our children during the preschool years, we may find it difficult to forgo in later states the level of control that once afforded us so much satisfaction.”
—Melinda M. Marshall (20th century)