Chapter 17


1:

What's the purpose of a test plan?

A1:

To paraphrase the IEEE 829 definition, the purpose of a test plan is to define the scope, approach, resources, and schedule of the testing activities and to identify the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the risks associated with the plan. In short, to tell and get agreement from the rest of the project team exactly how the heck the test team intends to test the software.

2:

Why is it the process of creating the plan that matters, not the plan itself?

A2:

Because all the issues and questions defined in a test plan either impact or are influenced by other project functional groups or team members. Getting everyone to understand and agree to the contents of the plan is what matters. Privately creating a paper document and putting it on a shelf is not just a waste of time, but also jeopardizes the project.

3:

Why is defining the software's quality and reliability goals an important part of test planning?

A3:

Because left to their own, everyone will have different ideas of what quality and reliability mean to them. Since they're all different, they all can't be achieved.

4:

What are entrance and exit criteria?

A4:

These requirements must be met to move from one testing phase to another. A phase can't be left until its exit criteria are met. A new phase can't be entered until its entrance criteria are met.

5:

Name a few typical testing resources that should be considered when test planning.

A5:

People, equipment, offices and labs, software, outsourcing companies, and miscellaneous supplies.

6:

True or False: A schedule should be made to meet absolute dates so that there's no question when a testing task or phase is to start and when it is to end.

A6:

False. Because testing depends so much on other aspects of the project (for example, you can't test something until it's coded), a test schedule is best made relative to the delivery dates.



    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