30 Days of Agile testing, Day 12: Test documentation


Test documenation is rather important but I fear its maintenance can get too heavy.
I use both approaches : check list oriented during user story estimation.
I briefly warn about the scope or the kind of testing technique to use (depending on the coverage level wanted).
In the other hand, we write more detailled steps and expected results when filling a bug reports.
As acceptance criteria are supposed to be met when the piece of code is delivered, bug reports may become a good indicator of software quality.
The key is the keep documentation consistent enough so that anyone can have the latest version implemented in mind.
This is maybe only true for Agile environments where a lack of documentation is less important than a lack of communication.

1 Like