Rhino.Mocks Google Group

Re: Problem with stub and outref

robertbl...@gmail.com (devghost) — Fri, 08 Jan 2010 13:02:46 UT

Sorry for this late reply to this thread... But there was indeed no
problem
with the test, the ErrorMessages was set twice in the code.
Kind Regards
Robert

Re: RhinoMocks AAA extensions for VB.Net ?

robertbl...@gmail.com (devghost) — Fri, 08 Jan 2010 12:58:28 UT

Did you figure this out? If not, here is what I do (regarding the
first problem), create
a fake function that can be used in the Lambda expression. It's way
more ugly but it makes it work in VB.
Here's an example, in the FakeErrorMessage i call the method or
property that doesn't have
ant return value...

Re: Stubbing existing classes doesn't work like expected

bill.richa...@greyskin.co.uk (bill richards) — Tue, 05 Jan 2010 21:49:55 UT

Wigman,
from the tone of your response it seems that I have somehow offended
you. This was not my intention, I was merely attempting to highlight
the fact that had the code been develped in a TDD fashion you would
not have encountered this issue.

Re: [RhinoMocks] Re: Stubbing existing classes doesn't work like expected

timba...@gmail.com (Tim Barcz) — Tue, 05 Jan 2010 12:28:55 UT

It's it not that the stub is causing your test to fail ... It is that
the stub can't quite do its job until some prerequisites are met...the
one here that you are running into is that stubbed methods need to be
virtual ( this is so that dynamic proxy can proxy the method )
Tim

Re: Stubbing existing classes doesn't work like expected

wouter.wig...@gmail.com (Wigman) — Tue, 05 Jan 2010 07:39:37 UT

Well, excuse me, Bill. The Rhino documentation clearly states that
generating a stub will never fail a test. Well, it does! And there ARE
mock products that can actually create a thorough stub, stubbing all
methods of an existing class, virtual or not, so excuse me again for
my learning curve using Rhino. Saying test-driven developing means you

Re: [RhinoMocks] Deserialization error while using int[] as a parameter

prabu...@gmail.com (Praburaj Thiagarajan) — Tue, 05 Jan 2010 06:38:55 UT

Hi Tim,
I have a test case with the code:
My expectation setting for the call is like below.
Expect.On(MTInterface).Call(MT Interface.TestMethod(0, null, null, out
ResultDataset, out
ErrorMsg)).OutRef(ResultDatase t).Return(0).IgnoreArguments() .Constraints(Is.Equal(52),
Is.Anything(), Is.Anything(), Is.Anything(), Is.Anything());

Re: Stubbing existing classes doesn't work like expected

bill.richa...@greyskin.co.uk (bill richards) — Mon, 04 Jan 2010 22:06:42 UT

and just to add to these perfectly explanatory responses .... this i
the result of NOT developing your code in a test driven manner

Re: [RhinoMocks] Re: Stubbing existing classes doesn't work like expected

timba...@gmail.com (Tim Barcz) — Mon, 04 Jan 2010 20:48:53 UT

I'll be honest in that I don't run into this problem very often because I
almost always try to have an interface in there...and as Caio pointed out,
it's not a problem that shows up when programming interfaces.
Tim

Re: [RhinoMocks] Re: Stubbing existing classes doesn't work like expected

cai...@gmail.com (Caio Kinzel Filho) — Mon, 04 Jan 2010 19:53:48 UT

I think most of the time, when you are programming against interfaces
rather than against implementations, you will not have that problem,
once rhino.mocks can just implement that interface instead of
inheriting from your implementation

Re: Stubbing existing classes doesn't work like expected

wouter.wig...@gmail.com (Wigman) — Mon, 04 Jan 2010 19:49:39 UT

Ok, now I know, thanx a million! Too bad i have to adjust the
'visibility' of my methods just to get the testing part in order.

Re: [RhinoMocks] Deserialization error while using int[] as a parameter

timba...@gmail.com (Tim Barcz) — Mon, 04 Jan 2010 16:24:37 UT

Can you provide a failing test that I (we) can run?

Re: [RhinoMocks] Stubbing existing classes doesn't work like expected

j...@jonorossi.com (Jonathon Rossi) — Mon, 04 Jan 2010 15:02:46 UT

The Test method is not virtual, so RhinoMocks cannot override it to do
nothing.

Stubbing existing classes doesn't work like expected

wouter.wig...@gmail.com (Wigman) — Mon, 04 Jan 2010 14:40:32 UT

When stubbing a class i expect the original class code is not
executed. However, the following example does throw an exception("We
don't expect this to be thrown"). I thought stubs never failed a test.
What am I doing wrong here? How can i make Rhino stub the existing
class properly, so calling Test() does not give errors?

Deserialization error while using int[] as a parameter

prabu...@gmail.com (Prabu) — Mon, 04 Jan 2010 13:32:34 UT

Hi,
I am using Rhino mocks 3.5 for mocking our web service. I am using a
PartialMock and the mock works fine for other methods but fails for a
method which has int[] as an argument. On changing the argument to int
this works fine.
int TestMethod(int MethodIndex, IDValuePair[] MethodArguments, int[]
SecurityIds, out System.Data.DataSet ResultData, out string ErrorMsg);

Re: [RhinoMocks] Mock all instances of a class

timba...@gmail.com (Tim Barcz) — Mon, 28 Dec 2009 19:42:36 UT

"Do I need to mock the 3 objects?" Yes.