How much Test Documentation is typically done for Scrum
We are implementing Scrum in my company and I am the Testing Lead. I do not
see any information regarding how much test documentation is typically done
for Scrum.
Do most companies develop test cases or is Ad Hoc testing always used? Is
there information regarding testing documentation available on this site?
Please let me know.
Thanks,
Eileen
Hi Eileen
Scrum is a framework and is not prescriptive about how testing is done. However, it is clear that there is no separate tester role.
In practice, most Scrum Development Teams aim to do Test Driven Development, whether in terms of unit tests, BDD tests, or both.
The requirements for acceptance testing are normally included in the Definition of Done, although specific acceptance criteria for each requirement are often negotiated between the Development Team and the Product Owner as well.
Scrum does not define how much test documentation is required. It is up to the team to decide how/what testing is done. It can be part of the definition of done. Testing standards could also be imposed by the organization rather than the team.
Going from personal experience rather than scrum theory: in my teams, our QA members decided on the test cases used. As Product Owner, I used the acceptance criteria in the stories to determine if it was done or not and trusted QA to cover outlier cases. Since then we added to the Definition of Dona: all JUnit tests must pass and test cases documented and passed in spira (a QA tool).
Note that scrum does not recognize QA or Testing Lead as being separate or different from the dev team. This is important because everyone must recognize it's not done until it's releaseable. The reality of our organization is that we have separate dev and QA roles, but the coders now recognize that it's not enough for them to just complete coding, they have to ensure there is enough time, and information, for the new functionality to be tested. Not that they always accomplish that...
Scrum guide states:
"Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all
Increments work together.
As Scrum Teams mature, it is expected that their definitions of “Done” will expand to include
more stringent criteria for higher quality. Any one product or system should have a definition of
“Done” that is a standard for any work done on it."