Exercises


graphics/exercise.gif

3-1. Identify the documents and models that are available for a system you want to test. For those pieces that are missing, determine how you might provide the required information.

3-2. Prioritize the objectives for your project and product.

3-3. Continue the development of your test plan by building a chart that lists all of the "products" that will be available for testing. A second column could be used to list the testing techniques that will be applied to test the product. It will be left blank for now. Is your project iterative? Is it incremental? If it is iterative, there should be a column that summarizes the results of applying each technique during each iteration. If it is incremental, there should be a separate table for each increment of the system since they will be developed independently.

3-4. What risk level would you assign to the Sprite, PuckSupply, Puck, and Velocity classes for Brickles?



A Practical Guide to Testing Object-Oriented Software
A Practical Guide to Testing Object-Oriented Software
ISBN: 0201325640
EAN: 2147483647
Year: 2005
Pages: 126

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