Rhino.Mocks Google Group

Re: Stubbing existing classes doesn't work like expected

2010-01-05T21:49:55Z

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

2010-01-05T12:28:55Z

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

2010-01-05T07:39:37Z

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

2010-01-05T06:38:55Z

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

2010-01-04T22:06:42Z

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

2010-01-04T20:48:53Z

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

2010-01-04T19:53:48Z

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

2010-01-04T19:49:39Z

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

2010-01-04T16:24:37Z

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

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

2010-01-04T15:02:46Z

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

Stubbing existing classes doesn't work like expected

2010-01-04T14:40:32Z

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

2010-01-04T13:32:34Z

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

2009-12-28T19:42:36Z

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

Mock all instances of a class

2009-12-28T19:30:24Z

Hi,
I have a test with 3 domain object of same class and I need to mock
the same method, by same way in all these objects. Do I need to mock
the 3 objects? Is there a way to mock the class, and then, all object
will call the mocked method??
Thanks,
Weverton

Re: Difference between t.Stub and t.Expect

2009-12-22T22:54:09Z

Sorry - i missed the end of you reply. Just read it through to the
end where you mentioned about the x.Expect.Return.Times(y).
I've never tried that, but it seems more granular and specific than my
'push my object through and hope the data is right when it comes out
the other end' way.
Thanks for that!