What are the best practices around "Acceptance Testing" in order to ensure that increment is ready to be shipped/released to production?
By including Acceptance Testing as part of the Sprint Backlog (either as tasks or as DoD) -
- Should it be completed "increment" that should be offered for Acceptance Testing or should it be done PBI by PBI?
- What about End to End testing for the final increment? When and how same should be conducted?
Here my input, good points.
The acceptance testing need to be written by the development team, the development team is the owner of the sprint backlog and accept it , the development team accept stories and each story has the testing included itself, the transformation from story to increment is clear for all in order of the DoD, so at the end of each sprint the PO accept or reject the increment according to the DoD., the stories transformed to increment are potential to move to production immediately if the company decide it, on real circumstances, so, the unit test, the integration testing, the regression testing are done at this time.
The end to end testing its need to be performed continuously into the each sprints, the continue delivery is the best concept around its,
The acceptance testing is part of each story and it need to be performed into of the sprint
> Should it be completed "increment" that should be offered
> for Acceptance Testing or should it be done PBI by PBI?
From your reading of the Scrum Guide, what ought to be acceptable for potential release...the PBI or the increment? What do you think the answer means for quality control? Might there be different levels of "Done"?