Software Development Cross Solution - Index of - Free

mock objects
We need lots of different, but similar, objects
The problem right now is that we have a sequence like this:
304 Chapter 8
processOrder(...)
Order
Processor
getGC(...)
saveGC(...)
Test DB
Utilities
processOrder(...)
saveOrder(...)
What if we generated objects?
return a specific
GC with certain
values
do nothing...
Instead of writing all these DBAccessor implementations,
what if we had a tool—or a framework—that we could tell
to create a new object, conforming to a certain interface (like
DBAccessor), and that would behave in a certain way, like
returning a gift card with a zero balance provided a certain
input was passed in?
Your test code can use this
object like any other... it
implements DBAccessor and
looks just like a real class that
you’d write yourself.
fake-save the GC
This is all fake, but since the
order processor has to call
these methods, we need an
implementation of DBAccessor.
Mock
Object
Download at WoweBook.Com
Here’s where the problem is: for each
different type of scenario, we need
a different test class to return the
right kind of gift card.
Your testing code tells the
framework what it needs.
TestGoodDBAccessor
+ getGC(gcId : int) :GiftCard
+ saveGC(card : GiftCard) :void
TestInsufficientDBAccessor
+ getGC(gcId : int) :GiftCard
+ saveGC(card : GiftCard) :void
TestInvalidDBAccessor
+ getGC(gcId : int) :GiftCard
+ saveGC(card : GiftCard) :void
I want a DBAccessor implementation that
returns a GiftCard with a zero balance, please.
Here’s an object... if you
call getGC() with a value
of “12345,” it will do just
what you want.
Most languages have a
framework just like this—just
Google “mock objects.”
Mock Object
Framework