ExpectAndReturn MockObject after myMock.Object

Hi,
I have tried this with version 3.0.2 and it works,
What version are you using?
What is the error that you are receiving?

I am using 3.0.2.1.

I am not getting an error, but the method is not getting mocked. I know this because the method I have mocked is hitting the database and I am getting a VerifyException for the mocked object.


I cant use trace because trace is not working with the version I have.

What Verify exception are you getting?

RemoteNet.Northrop.IbisWork.UnitTests.Domain.Model.ProcessContextFixture.CannotDeleteIfHasProcedures : TypeMock.VerifyException :
TypeMock Verification: Method RemoteNet.Northrop.IbisWork.Domain.Model.Process.HasProcedures() has 1 more expected calls

This exception doesnt relate to the example I gave in the originating post because I wanted to simplify things but the concept is still the same.

Hi,
This cannot be the correct message, as MockObjects are Strict and should fail once you call an unmocked method.
Are you sure that your small example fails? Can you send an example that fails

I tried creating a sample and could not reproduce the problem either, so I started looking at how my code was different than the sample I created. It turns out that a previous bug had re-inserted itself into the code, possibly because of a rollback, but MockManager.Verify was getting called on test teardown as opposed to fixture teardown. This was causing the tests to get screwed up. So this problem has been resolved, it was our fault.

However, the test sample that I created did proove that mock objects are not operating strictly as you have stated in your last post.

My sample creates a Mock object and then I can call methods on that MockObject that do not have an expectation set. I can send the sample to you if this is not the expecte behavior.

Sorry for wasting your time on the other problem.

Hi,
There are actually two kinds of MockObjects.
1. From abstract and interfaces - these are always Strict
2. From other classes - in this case MockObject is just a shortcut for setting a mock and then creating the object. In this case the MockObject is not Strict

The reason for this is that interface methods just dont exist - so there is nothing to call, while other cases there is actual code to call.