exer-student Software Testing Techniques_2013 《软件测试》课件.pdf

Introduction to Software Testing Paul Ammann and Jeff Offutt Solutions to Exercises Student Version November 26, 2013 Copyright Ammann Offutt, 2002-2009, all rights reserved. 2 Tell me and I may forget. Show me and I may remember. Involve me and I will understand – Chinese proverb Introductory Note As readers will undoubtedly note, as of November 26, 2013, a few problems still do not have complete solutions. Paul (pammann@) and Jeff (offutt@) welcome your help with new solutions and corrections to our errors. In fact, we hope this will be viewed as a community resource and welcome any kind of feedback. We distinguish between “student solutions” and “instructor only” for the convenience of both. Students can work homeworks then check their own answers. Instructors can assign homeworks with some confidence that students will do their own work instead of looking up the answer in the manual. 3 Exercises, Section 1.1 1. What are some of the factors that would help a development organization move from Beizer’s testing level 2 (testing is to show errors) to testing level 4 (a mental discipline that increases quality)? Instructor Solution Only 2. The following exercise is intended to encourage you to think of testing in a more rigorous way than you may be used to. The exercise also hints at the strong relationship between specification clarity, faults, and test cases. (a) Write a Java method with the signature public static Vector union (Vector a, Vector b) The method should return a Vector of objects that are in either of the two argument Vectors. Inst