Rexx is correct and that is what I meant by "setting up the
expectation". You need a two-step setup process for your mocks when
using easymock.
This question was easymock specific, but if you are coming across
questions about issues wrt testing and Turbine I think this is a great
place to talk about them. There is some other stuff hidden away on
the apache wiki wrt to testing also. The testing page needs some
additional examples/information added. Maybe you would be willing to
add a few more examples for the tutorial?
I think well written frameworks should provide stable/standard ways to
be incorporated into programmer tests ( or at the least, stay out of
the way ( maybe that is the best behavior for a framework, from a
testing perspective )).
>>>>> On Thu, 02 Oct 2003 14:36:44 -0400, brian janaszek <[EMAIL PROTECTED]> said:
> On Thu, 2003-10-02 at 14:27, Rex Madden wrote:
>> After data.getUser(), you need to tell the control what to return
>> using control.setReturnValue(myUserObject). So now it's:
>>
>> data.getUser(); control.setReturnValue(myUserObject);
>> control.verify();
>>
>> By the way, this is more of an EasyMock question than a Turbine
>> question, and should probably be on the EasyMock group.
>>
> Thanks for information. I thought I'd be venturing into the realm
> of EasyMock questions, but since there is an EasyMock "tutorial" on
> the Turbine site (albeit brief), I thought I'd ask around here
> first.
> b
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
