-
Book Overview & Buying
-
Table Of Contents
Software Testing Strategies
By :
The common way of thinking about testing, or perhaps the loudest, leftover from the previous century, was to “plan the work and work the plan.” People doing testing would run through a sequence of steps, and the end would have an “expected result.” If those two don’t match, file a bug. Seems pretty easy, right?
Except it never seemed to work out that way.
Instead, the person doing the work would just try to follow the steps, and they wouldn’t work. Report the bug, wait for a new build, then try to recreate where they were in the procedure. We wrote “seemed” earlier because that was the past. Today, many of our customers have broad general success on the first pass with their software. The problem is that idea of an “expected result.” As we mentioned in Chapter 1, every documented test with an expected result has a hidden second assertion “...and nothing else odd happened.” If you...