Lessons Learned in Software Testing: A Context-Driven Approach

Lessons Learned in Software Testing: A Context-Driven Approach

Cem Kaner, James Bach, Bret Pettichord

Language: English

Pages: 320

ISBN: 0471081124

Format: PDF / Kindle (mobi) / ePub

Decades of software testing experience condensed into the most important lessons learned.

The world's leading software testing experts lend you their wisdom and years of experience to help you avoid the most common mistakes in testing software. Each lesson is an assertion related to software testing, followed by an explanation or example that shows you the how, when, and why of the testing lesson. More than just tips, tricks, and pitfalls to avoid, Lessons Learned in Software Testing speeds you through the critical testing phase of the software development project without the extensive trial and error it normally takes to do so. The ultimate resource for software testers and developers at every level of expertise, this guidebook features:
* Over 200 lessons gleaned from over 30 years of combined testing experience
* Tips, tricks, and common pitfalls to avoid by simply reading the book rather than finding out the hard way
* Lessons for all key topic areas, including test design, test management, testing strategies, and bug reporting
* Explanations and examples of each testing trouble spot help illustrate each lesson's assertion












teams clear charters Automate for immediate impact You may have more test tools than you realize 104 106 107 108 109 109 110 111 111 112 112 113 113 114 115 116 117 117 119 120 121 122 122 123 124 125 126 126 Chapter 6 Documenting Testing Lesson 142 Lesson 143 Lesson 144 Lesson 145 Lesson 146 Lesson 147 Lesson 148 Lesson 149 To apply a solution effectively, you need to understand the problem clearly Don’t use test documentation templates: A template won’t help unless you don’t need it Use test

in tone, poorly explained, or inadequately researched or suggest that you’re blowing small issues out of proportion will create a negative impression in the minds of the people who approve your raises and promotions. 65 71208_Kaner_CH04I 66 11/21/01 4:24 PM Page 66 L E S S O N S L E A R N E D I N S O F T WA R E T E S T I N G Everyone benefits if you take the time to research and write your reports well. L n esso 56 Your advocacy drives the repair of the bugs you report. Any bug report

weak. Your data could be less random than you expected. Check and see (Park and Miller 1988). Kaner and Vokey (1984) provide a thoroughly tested set of parameters for a random number generator that you can program easily in Java or any other language that handles high-precision integer arithmetic. ■■ Tests are easier to repeat when the data is pregenerated. We’ve seen test scripts that changed the test every time they ran. If you can’t pregenerate the data, you need to take other measures to

programmers do (and don’t do) before delivering builds. Some programming groups do extensive unit testing before releasing a new build to testers. Others don’t. Some programming groups do a smoke test as part of their build process. Others don’t. The programming group that you work with does what it does. Don’t assume that they have or have not done certain types of tests or taken a certain level of care in preparing a build for you. Find out their process and base what you do on your knowledge

of what they do. L n esso 172 Be prepared for the build. It’s important to have your test environments ready when the builds are ready. This is especially true in the Web space. In a fast-paced project, a test group without a well-managed test environment is useless. L n esso 173 Sometimes you should refuse to test a build. Occasionally, you will reject a build and refuse to test it. There can be sound technical reasons for doing this: ■■ If the importance of this build is that it adds

Download sample