I think it's more about having a unified set of test cases, using in the best possible way the particular API exposed by each framework.
Can be useful for learning and comparing, but also for people migrating from one to the other. Moq *tests* are written for xUnit. That doesn't mean that you cannot use Moq with any test framework you like. It has NO dependency whatesoever on xUnit. /kzu -- Daniel Cazzulino | Developer Lead | XML MVP | Clarius Consulting | +1 425.329.3471 On Tue, Feb 10, 2009 at 2:51 PM, gerry_lowry (alliston ontario canada) < [email protected]> wrote: > > Hi andreister ~~ what do you mean by "a unified set of tests > written against Moq, NMock2, Rhino Mocks and > TypemockIsolator"? > > To me, "unified" is like one size fits all ... how is that possible when > the various mocking frameworks have varying syntax and different underlying > frameworks, e.g., AFAIK, MoQ depends on xUnit. > { > http://www.clariusconsulting.net/blogs/kzu/archive/2008/04/22/MoQnowusesxUnitforitsunittests.aspx > } > > Please explain what you mean by "unified". > > Thank you. > > regards .... gerry (lowry) > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/RhinoMocks?hl=en -~----------~----~----~----~------~----~------~--~---
