Comments on: Fighting Bad Test Documentation http://www.satisfice.com/blog/archives/19 The Consulting Software Tester Sat, 22 Nov 2008 09:16:08 +0000 http://wordpress.org/?v=2.3.3 By: Sajeev Kesavan http://www.satisfice.com/blog/archives/19#comment-115877 Sajeev Kesavan Mon, 31 Mar 2008 09:51:53 +0000 http://www.satisfice.com/blog/archives/19#comment-115877 From my perspective , I see that documentation is very much required. Yes Bad documentation is Bad but good documentation is also Good.It is just not to secure a turn over , but shows necessary traceability , displays more often the coverage of tests, to understand the weightage of tests written for the various modules. Documentation should be a part of the testing and if we find documents is taking a lot of time, then its upto management to plan their test schedule including the time required for the documentation. Exploratory testing should be off the shelf outside the documents and interesting test scenarios that has identifies issues should again be documented. Thats my cents of experience. Agree with James on most of his points ,:"Demonstrate the value of concise test documentation (matrices, outlines). " and " Bad documentation is not good " and yes smart documentation is required. From my perspective , I see that documentation is very much required. Yes Bad documentation is Bad but good documentation is also Good.It is just not to secure a turn over , but shows necessary traceability , displays more often the coverage of tests, to understand the weightage of tests written for the various modules. Documentation should be a part of the testing and if we find documents is taking a lot of time, then its upto management to plan their test schedule including the time required for the documentation.

Exploratory testing should be off the shelf outside the documents and interesting test scenarios that has identifies issues should again be documented. Thats my cents of experience.

Agree with James on most of his points ,:”Demonstrate the value of concise test documentation (matrices, outlines). ” and ” Bad documentation is not good ” and yes smart documentation is required.

]]>