Software Development Cross Solution - Index of - Free

unit testing
Your first test...
The first step in writing a test is to figure out what exactly it
is you should be testing. Since this is testing at a really finegrained
level—unit testing—you should start small. What’s
the smallest test you could write that uses the order
information you’ve got to store as part of the first task? Well,
that’s just creating the object itself, right? Here’s how to test
creating a new OrderInformation object:
This is a JUnit
test... a single
method that tests
object creation.
278 Chapter 8
package headfirst.sd.chapter8;
import org.junit.*;
public class TestOrderInformation {
@Test
public void testCreateOrderInformation() {
OrderInformation orderInfo = new OrderInformation();
}
}
Wait—what are you doing? There’s no way this
test is going to work; it’s not even going to compile.
You’re just making up class names that don’t exist.
Where did you get OrderInformation from?
You’re exactly right! We’re writing
tests first, remember? We have no code. There’s no way
this test could (or should) pass the first time through. In fact,
this test won’t even compile, and that’s OK, too. We’ll fix it
in a minute. The point here is that at first, your test...
Download at WoweBook.Com
Keep it as simple
as possible: just
create a new
OrderInformation
object.