Software Development Cross Solution - Index of - Free

where to place your test code
Remember, as
long as you’re
using the test
DBAccessor
this is just a
placeholder.
The test wants
a zero-balance
gift card at
the end. So we
simulate that.
Hmm, this isn’t
good; this is what
the test wants but
we’re obviously going
to have to revisit
this. We’ll need
another test.
298 Chapter 8
}
Getting to Green...again.
Now you’ve got a way to isolate the OrderProcessor class from the
database. Implement the processOrder() method using the right
database strategy.
// existing code
private DBAccessor dbAccessor;
public void setDBAccessor(DBAccessor accessor) {
dbAccessor = accessor;
}
public Receipt processOrder(OrderInformation orderInfo) {
}
GiftCard gc = dbAccessor.getGC(orderInfo.getGiftCardNumber());
dbAccessor.saveOrder(orderInfo);
// This is what our test is expecting
gc.setBalance(new BigDecimal(0));
dbAccessor.saveGC(gc);
Receipt receipt = new Receipt();
receipt.setConfirmationNumber(12345);
receipt.setPickupTime(new Date());
receipt.setGCBalance(gc.getBalance());
return receipt;
Q: I just don’t buy it. We just wrote a bunch of code that we
know is wrong. How is this helping me?
A: The test we wrote is valid—we need that test to work. The code
we wrote makes that test work so we can move on to the next one.
That’s the principle behind TDD—just like we broke stories into tasks
Download at WoweBook.Com
Remember, this is just the code
needed to get our test passing; it’s
OK that we’re going to have to
revisit this code for the next test.
to get small pieces, we’re breaking our functionality into small code
pieces. It didn’t take long to write the code to get the first test to pass
and it won’t take long to refactor it to get the second one to pass, or
the third. When you’re finished you’ll have a set of tests that makes
sure the system does what it needs to, and you won’t have any more
code than necessary to do it.