Software Development Cross Solution - Index of - Free

all green, you’re done
It’s not easy bein’ green...
You did it—through the help of the strategy pattern, dependency injection (see the previous No
Dumb Questions), and mock objects, you have a really powerful, but not too bulky, suite of unit
tests. You now have piles of tests that make sure your system does what it’s supposed to be doing
at all times. So to keep your system in line:
1
2
3
4
5
310 Chapter 8
Always write a test before you write the real production code.
Make sure your test fails, and then implement the simplest thing that will
make that test pass.
Each test should really only test one thing; that might mean more than one
assertion, but one real concept.
Once your’re back to green (your test passes) you can refactor some
surrounding code if you saw something you didn’t like. No new
functionality—just cleanup and reorganization.
Start over with the next test. When you’re out of tests to write, you’re done!
When all of your tests pass, you’re done
Before we never really had a way of knowing when we were finished. You wrote a bunch of
code, probably ran it a few times to make sure it seemed to be working, and then moved on.
Unless someone said something bad happened, most developers won’t look back. With testdriven
development we know exactly when we’re done—and exactly what works.
I’m pretty sure I’m done.
Things seem to be working OK.
Bob again...
Which do you think is better?
vs
File Edit Window Help Bliss
hfsd> java -cp junit.jar;. org.junit.runner.JUnitCore
headfirst.sd.chapter8.TestOrderProcessor
JUnit version 4.4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . .
Time: 0.321
OK (86 test)
hfsd>
Download at WoweBook.Com
Our test suite in action
* If you said Bob, please donate this book to your library.