Can anyone point me to a resource that shows an example of how Pex can be used in conjunction with MoQ? Thanks
相关问题
- Mockito : How to test my Dao with mocking?
- FakeItEasy - Having an interface fake inherit from
- How can you mock the methods from a class if you h
- How to mock IFindFluent interface
- Functional Test - Mock service does not persist in
相关文章
- How to replace file-access references for a module
-
EF6 DbSet
returns null in Moq - Mocking indexed property
- Mocking nested properties with mock
- Can I use moq's InSequence() with MockBehavior
- How to set the value of a query string in test met
- Using Moq to Stub an interface method [duplicate]
- How to spy on window.scrollTo in Jest?
Pex uses Moles for isolation (mocking). One can still use MoQ alongside Moles. It's actually preferred to use a framework like MoQ for stubbing and mocking when the code can allow for it, leaving only Moles for the stuff MoQ can't isolate (sealed classes, non-virtual methods, private members, etc).
To backup my statements, Peli de Halleux (a member of the Pex and Moles project), mentions doing the same thing over on MSDN forums.
I have been using Moles and you can code with both frameworks in a unit test. But this probably isn't much help as you are asking specifically about Pex, which I haven't tried yet. Is it possible to modify the unit tests Pex creates and add the MoQ code after the fact?
When writing parametrised Pex tests make sure that when you get those "Uninstrumented methods" related to Moq calls, you can easily click on "Ignore uninstrumented method..." that will add assembly attribute to your test project and it will simply ignore Moq methods thus making them usable in your tests.
I've done it myself and tests run as expected.