Summary


Developing a test plan, even for a small project, is a large task that can't be taken lightly. Sure, it would be easy to fill in a template's blanks and in a few hours be printing out copies of a test plan, but that's missing the point. Test planning is a job that should involve all testers and key players from across the entire product team. Taking the time to do it properly may take many weeks or even months. But, building a comprehensive understanding and an agreement of what's to be tested, why it's to be tested, and how it's to be tested early in the product development cycle will make the test effort run much more smoothly than if the process is rushed. Remember, it's the process of creating the test plan, not the resulting document, that's important.

If you're new to testingand you probably are if you're reading this bookyou likely won't be responsible for developing an overall software test plan. You should, however, be prepared to provide input on all the topics presented in this chapter to your test lead or manager. You'll be responsible for testing certain aspects and features of the software; the schedule you make, the resources you need, and the risks you take will all eventually bubble up to the overall test plan.



    Software Testing
    Lessons Learned in Software Testing
    ISBN: 0471081124
    EAN: 2147483647
    Year: 2005
    Pages: 233

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net