Browse by Tags
All Tags »
mocking »
frameworks (
RSS)
Sorry, but there are no more tags available to filter with.
-
|
Just wanted to quickly note that I tracked down the performance issue in Rhino.Mocks and patched it . I also updated the original post with the new numbers. Enjoy!
|
-
|
UPDATE: I tracked down the issue and committed a patch to Rhino.Mocks. Rhino.Mocks is now much more competetive performance wise, our CI build time nearly halved, and about 4 minutes out of 7 of our test time has disappeared. New numbers below. I've...
|
-
|
Currently in Rhino.Mocks, making mocks fire events and ensuring that an event on your SUT was fired are both awkward and verbose at best. Here is an example of both things at once: [Test] public void ViewFiresBeginDrag_Always_FiresChangedEvent() { IEventRaiser...
|
-
|
Daniel Cazzulino , author of Moq posted a good comment on my last post where I suggested looking into a Mockito like syntax for .NET Mock Frameworks. On the surface, Mockito's approach seems good. But if you do the "true" comparison, you'll...
|
-
|
(Note: I'm going to speak about .NET mock projects here for the most part, but most of them have Java quasi-equivalents.) The original mocking frameworks like NMock required you to setup expectations by passing strings for method names. This was fragile...
|
More Posts