Software Development Cross Solution - Index of - Free

think about estimating
Even
though you
don’t know
exactly
how this
code works,
it should
be clear
what it
should do.
package test.com.orionsorbits.mercurymeals;
import com.orionsorbits.mercurymeals.*;
import org.junit.*;
public class TestMercuryMeals {
String[] options;
String flightNo;
}
@Before
public void setUp() {
options = {"Fish and chips");
flightNo = "VS01";
}
@After
public void tearDown() {
options = null;
flightNo = null;
}
@Test
public void testOrderRegularMeal()
throws MealOptionNotFoundException, OrderNotAcceptedException {
}
MercuryMeals mercuryMeals = MercuryMeals.getInstance();
Order order = mercuryMeals.createOrder();
MealOption mealOption = mercuryMeals.getMealOption(options[0]);
if (mealOption != null) {
order.addMealOption(mealOption);
} else {
throw new MealOptionNotFoundException(mealOption);
}
order.addKeyword(flightNo);
if (!mercuryMeals.submitOrder(order)) {
throw new OrderNotAcceptedException(order);
}
398 Chapter 11
Your job was to create a unit test that exercises all of the functionality your
user stories need. The “Order Regular Meal” test creates an order, adds a
regular meal option to it (in this case, “Fish and chips”), and then submits
the order to Mercury Meals.
These exceptions are just ways
to cause the test to fail, and
say something in the Mercury
Meals API didn’t work.
Download at WoweBook.Com
Title:
Est:
Priority:
Here’s the user
story you’re testing
Mercury Meals
functionality for.
Order Regular Meal
12 days
10
Create an order and
get the single meal
option that was set
up prior to the test
being run.
Add the “Fish and chips” meal
option to the order, tie the
order to the flight number,
and then submit the order to
Mercury Meals.