Final UAT
I'm confused about the final UAT.
Is it an End to End testing, in which case new Test Cases need to be written to cover all possible scenarios or are the individual SPRINT acceptance testings sufficient?
My further questions:
1. When in the SCRUM project do we start writing these end-to-end testcases? Could be hundreds depending on the possible scenarios)
2. Does the Business write these from scratch or can they piggy-back on the QA test scripts?
3. At what point do we decide what the final product is? The hundreds of test-cases might have to be rewritten constantly. Is there a Code-Freeze?
Cheers
The purpose of each sprint (from the very first one) is to produce a potentially shippable increment.
What does it mean for you ?
Thanks Olivier,
That would mean that a final UAT covering the end-to-end product testing would not be necessary...
If the tests are automated - then there's a little chance an end-to-end testing would be required as a big separate activity (you'll organically grow toward that).
In a real life, not all of the companies have the luxury of creating auto-tests. What means the scope of testing grows per sprint.
So, I wouldn't say there's no need in running end-to-end testing, but you should keep in mind each sprint is to deliver a potentially shippable increment. In other words,
1. Each sprint should be potentially shippable (=tested)
2. All sprints (including the last one) should deliver an increment