Repo for managing Moq 4.x
The most popular and friendly mocking library for .NET
var mock = new Mock();
// WOW! No record/replay weirdness?! :) mock.Setup(library => library.DownloadExists("184.108.40.206")) .Returns(true);
// Use the Object property on the mock to get a reference to the object // implementing ILoveThisLibrary, and then exercise it by calling // methods on it ILoveThisLibrary lovable = mock.Object; bool download = lovable.DownloadExists("220.127.116.11");
// Verify that the given method was indeed called with the expected value at most once mock.Verify(library => library.DownloadExists("18.104.22.168"), Times.AtMostOnce());
Moq also is the first and only library so far to provide Linq to Mocks, so that the same behavior above can be achieved much more succinctly:
ILoveThisLibrary lovable = Mock.Of(l => l.DownloadExists("22.214.171.124") == true);
// Exercise the instance returned by Mock.Of by calling methods on it... bool download = lovable.DownloadExists("126.96.36.199");
// Simply assert the returned state: Assert.True(download);
// If you really want to go beyond state testing and want to // verify the mock interaction instead... Mock.Get(lovable).Verify(library => library.DownloadExists("188.8.131.52"));
You can think of Linq to Mocks as "from the universe of mocks, give me one whose behavior matches this expression".
Checkout the Quickstart for more examples!
Moq (pronounced "Mock-you" or just "Mock") is the only mocking library for .NET developed from scratch to take full advantage of .NET Linq expression trees and lambda expressions, which makes it the most productive, type-safe and refactoring-friendly mocking library available. And it supports mocking interfaces as well as classes. Its API is extremely simple and straightforward, and doesn't require any prior knowledge or experience with mocking concepts.
The library was created mainly for developers who aren't currently using any mocking library (or are displeased with the complexities of some other implementation), and who are typically manually writing their own mocks (with more or less "fanciness"). Most developers in this situation also happen to be quite pragmatic and adhere to state (or classic) TDD. It's the result of feeling that the barrier of entry from other mocking libraries is a bit high, and a simpler, more lightweight and elegant approach is possible. Moq achieves all this by taking full advantage of the elegant and compact C# and VB language features collectively known as LINQ (they are not just for queries, as the acronym implies).
Moq is designed to be a very practical, unobtrusive and straight-forward way to quickly setup dependencies for your tests. Its API design helps even novice users to fall in the "pit of success" and avoid most common misuses/abuses of mocking.
When it was conceived, it was the only mocking library that went against the generalized and somewhat unintuitive (especially for novices) Record/Replay approach from all other libraries (and that might have been a good thing ;)).
Not using Record/Replay also means that it's straightforward to move common expectations to a fixture setup method and even override those expectations when needed in a specific unit test.
You can read more about the "why" and see some nice screenshots at kzu's blog.
In-depth documentation is being added to the documentation website.
Moq uses Castle DynamicProxy internally as the interception mechanism to enable mocking.
Moq offers the following features: * Strong-typed: no strings for expectations, no object-typed return values or constraints * Unsurpassed VS IntelliSense integration: everything supports full VS IntelliSense, from setting expectations, to specifying method call arguments, return values, etc. * No Record/Replay idioms to learn. Just construct your mock, set it up, use it and optionally verify calls to it (you may not verify mocks when they act as stubs only, or when you are doing more classic state-based testing by checking returned values from the object under test) * VERY low learning curve as a consequence of the previous three points. For the most part, you don't even need to ever read the documentation. * Granular control over mock behavior with a simple MockBehavior enumeration (no need to learn what's the theoretical difference between a mock, a stub, a fake, a dynamic mock, etc.) * Mock both interfaces and classes * Override expectations: can set default expectations in a fixture setup, and override as needed on tests * Pass constructor arguments for mocked classes * Intercept and raise events on mocks * Intuitive support for