Skip to main content

Acceptance Testing?

Last post 04:08 pm June 29, 2016 by Ian Mitchell
2 replies
01:16 pm June 29, 2016

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?

Pankaj


02:09 pm June 29, 2016

Hi Pankaj,

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,

Best,
Gabriel



The acceptance testing is part of each story and it need to be performed into of the sprint


04:08 pm June 29, 2016

> 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"?


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.