Thanks to those that responded over the last few weeks. I ended up writing a blog post about my findings, since I had to do so much digging that it seemed like I might as well summarize them in the hopes of helping others. The chart I posted organizes my findings: One caveat, which I … Read more
The simplest thing is just to return a completed task with the expected result: var responseTask = Task.FromResult(response); I imagine reason this hangs is that the mocked task is never started and hence the given func is not run. You could start it in your test: var responseTask = MockRepository.GenerateMock<Task<HttpResponseMessage>>(taskFunc); responseTask.Start(); However there’s no reason … Read more
newContact.AssertWasCalled(x => { var dummy = x.Forenames; }, options => options.Repeat.AtLeastOnce()); Repeat.Any does not work with AssertWasCalled because 0 counts as any… so if it WASN’T called, the AsserWasCalled would return TRUE even if it wasn’t called.
Although I fundamentally agree with Nick Holt’s answer, I thought I should point out that mockito allows to do what you ask with the following call : Foo mock = Mockito.mock(Foo.class, withSettings().extraInterfaces(Bar.class)); Obviously you’ll have to use the cast: (Bar)mock when you need to use the mock as a Bar but that cast will not … Read more
Runtime is the version of the CLR (or .NET framework) the DLL needs (usually as a minimum), version is the DLL’s version. So long as you have the minimum runtime installed, it should be usable. However as a general rule it is usually best to select the latest version of the library for the latest … Read more
There are three ways: You can reset the expectations by using BackToRecord I have to admit that I never really used it because it is awkward. // clear expectations, an enum defines which _stubRepository.BackToRecord(BackToRecordOptions.All); // go to replay again. _stubRepository.Replay(); Edit: Now I use it sometimes, it is actually the cleanest way. There should be … Read more
I’m not a Castle expert nor compiler guru, but I believe the issue is a little bit of magic that is hidden inside the RhinoMocks.Tests assembly: From https://github.com/ayende/rhino-mocks/blob/master/Rhino.Mocks.Tests/TestInfo.cs using System.Runtime.CompilerServices; using Rhino.Mocks; [assembly: InternalsVisibleTo(RhinoMocks.StrongName)] And for completeness sake, RhinoMocks.StrongName is defined as: /// <summary> /// Used for [assembly: InternalsVisibleTo(RhinoMocks.StrongName)] /// Used for [assembly: InternalsVisibleTo(RhinoMocks.NormalName)] /// … Read more
Using MoQ it looks something like this: var request = new Mock<HttpRequestBase>(); request.Expect(r => r.HttpMethod).Returns(“GET”); var mockHttpContext = new Mock<HttpContextBase>(); mockHttpContext.Expect(c => c.Request).Returns(request.Object); var controllerContext = new ControllerContext(mockHttpContext.Object , new RouteData(), new Mock<ControllerBase>().Object); I think the Rhino Mocks syntax is similar.
Definitely a good list. Here are a few thoughts on it: Write the test first, then the code. I agree, at a high level. But, I’d be more specific: “Write a test first, then write just enough code to pass the test, and repeat.” Otherwise, I’d be afraid that my unit tests would look more … Read more
As per this … Put simply there is a difference between Mock and Stub objects and RhinoMocks recognizes that allowing us to write tests that better state their purpose. Mock objects are used to define expectations i.e: In this scenario I expect method A() to be called with such and such parameters. Mocks record and … Read more