Hi guys, how are you doing? What is the approach towards writing a good testplan? I mean what info and considerations should we take into account for writing a good TestPlan?
thanx and have a Great Weekend.
There is one trick about the checklist you are talking about. It is great reminder of things to take into account while doing test planning. It is not so great for creating the plan as document to be stored and red however. If you want to write test plan that is considered to be great by it's readers - the most significant aspect - how to make it readable. There are no sense to describe in test plan something that the reader don't want to know - you will only make them miss the important part of the plan or even not to read the plan through. There are a sense to use company wide templates, to use visual pictures, tables even colours, styles - instead of pages of plain text using testing jargon (domain testing) or well-know/established info like problem reporting style (given that you have established one in your company)
[ QUOTE ]
There are no sense to describe in test plan something that the reader don't want to know - you will only make them miss the important part of the plan or even not to read the plan through.
[/ QUOTE ]
I hate to be the one to bring you bad news, but I'd say only about 10% - 25% of the expected audience will actually read through the test plan even if you spend days making it easy to read. This includes testers who are supposed to be reading it for overall strategy.
Most people in your audience will simply read the executive summary and that's it. The second level of interest will simply scan the document looking for information pertinent to specific questions or tasks. For instance, a Sys Admin will more than likely completely skip the sections detailing functional, unit, and usability testing preferring to read only the sections detailing test environments and performance/concurrency/load/stress/recovery testing. A BA, however, will usually limit themselves to functional testing and project planning elements.
I didn't [img]/images/graemlins/frown.gif[/img]
I do believe however this topic deserves more attention now as things changes to agile - era of long formal documents that none reads seems to be gone. ...will consider to blog about it.