Software Development Cross Solution - Index of - Free

keep it simple
You can just make
up a gift card
number here...
The simplest thing
here is to not worry
about the balance
on the card... this
is just testing the
simplest version of
order processing.
292 Chapter 8
Red
Your job was to implement a test that will verify your software can
process a simple order.
// existing tests
@Test
public void testSimpleOrder() {
}
// First create the order processor
OrderProcessor orderProcessor = new OrderProcessor();
// Then you need to describe the order that should be placed
OrderInformation orderInfo = new OrderInformation();
orderInfo.setCustomerName(“Dan”);
orderInfo.setDrinkDescription(“Bold with room”);
orderInfo.setGiftCardNumber(12345);
orderInfo.setPreferredStoreNumber(123);
// Hand the order off to the order processor and check the receipt
Receipt receipt = orderProcessor.processOrder(orderInfo);
assertNotNull(receipt.getPickupTime());
assertTrue(receipt.getConfirmationNumber() > 0);
assertTrue(receipt.getGCBalance().equals(0));
Q: How can you just assume that the gift card has the right
amount on it? Isn’t that an assumption? Aren’t those bad?
A: We’re writing our first test, and then we need to make it pass.
So, we’re sort of assuming that the gift card has enough on it, but
since we’re about to implement the backend code, we can make
sure it does then. What we are setting ourselves up for is some
refactoring. Once we get this test passing we’ll obviously need to add
a test for a gift card that doesn’t have enough money on it. When we
do that, we’ll certainly have to revisit the code we wrote to get this
test going and rework it to support different gift cards and different
values. But, this is going to take some thought. Read on...
Download at WoweBook.Com
Q: There are a bunch of values in that test that aren’t
constants—should I care?
A: Yes, you should. To keep the code sample short we didn’t
pull those values into constants, but you should treat your test
code just like production code you write and apply the same style
and discipline. Remember, this isn’t throwaway code; it lives in the
repository with the rest of your system, and you rely on it to let you
know if things aren’t working right. Treat it with respect.