Skip to content
Repo for managing Moq 4.x
C# Other
Find file
Latest commit 7c9e2a4 Apr 8, 2016 @kzu kzu Merge pull request #255 from urasandesu/master
Fix the out parameter issue of delegate mock
Failed to load latest commit information.
.nuget Added missing nuget executable Aug 21, 2013
Common @ 354e54d Finally added automated nuget package builds. Aug 21, 2013
Lib Re-normalize repository Dec 13, 2013
Samples Re-normalize repository Dec 13, 2013
Source.Silverlight Fix reference to Castle.Core 3.3.3 for SL5 project Oct 22, 2015
Source Fix the out parameter issue of delegate mock Apr 9, 2016
Tools Re-normalize repository Dec 13, 2013
UnitTests.Silverlight upgrading to Castle.Core 3.3.3 Sep 26, 2015
UnitTests.Visualizer Re-normalize repository Dec 13, 2013
UnitTests Fix the out parameter issue of delegate mock Apr 9, 2016
Visualizer Re-normalize repository Dec 13, 2013
.gitattributes Added CRLF settings to repo Jul 8, 2013
.gitignore Merge dev branch Aug 23, 2013
.gitmodules Finally added automated nuget package builds. Aug 21, 2013
License.txt License is BSD-3, not BSD-2 Sep 7, 2015
Moq.Help.scproj Re-normalize repository Dec 13, 2013
Moq.nuspec Update projects for VS2013 Jun 19, 2015
Moq.shfb Re-normalize repository Dec 13, 2013
Moq.shfbproj Re-normalize repository Dec 13, 2013
Moq.sln Forced desktop build before silverlight build (to perform nuget restore) Aug 23, 2013
Moq.snk Merged branch for dynamic types. Jan 3, 2008
README.md Added gitter badge Jul 3, 2015
ReleaseNotes.md Updates for 4.3 Aug 6, 2014
build.cmd Point to latest msbuild engine. Aug 5, 2014
build.proj Remove trailing zero in revision if present Oct 21, 2015
moq-bigger.png Updated to use nuget packages for Castle and xUnit dependencies, as w… Aug 21, 2013
moq-small.png cleaned up AsMockExtensions Aug 9, 2009
moq.png tentative logo Aug 24, 2008

README.md

moq

The most popular and friendly mocking framework for .NET

NuGet downloads Version Join the chat at https://gitter.im/Moq

  var mock = new Mock<ILoveThisFramework>();

  // WOW! No record/replay weirdness?! :)
  mock.Setup(framework => framework.DownloadExists("2.0.0.0"))
      .Returns(true);

  // Hand mock.Object as a collaborator and exercise it, 
  // like calling methods on it...
  ILoveThisFramework lovable = mock.Object;
  bool download = lovable.DownloadExists("2.0.0.0");

  // Verify that the given method was indeed called with the expected value at most once
  mock.Verify(framework => framework.DownloadExists("2.0.0.0"), Times.AtMostOnce());

Moq also is the first and only framework so far to provide Linq to Mocks, so that the same behavior above can be achieved much more succintly:

  ILoveThisFramework lovable = Mock.Of<ILoveThisFramework>(l =>
    l.DownloadExists("2.0.0.0") == true);

  // Hand the instance as a collaborator and exercise it, 
  // like calling methods on it...
  bool download = lovable.DownloadExists("2.0.0.0");

  // 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(framework => framework.DownloadExists("2.0.0.0"));

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!

What?

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.

Why?

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 frameworks (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.

Where?

See our Quickstart examples to get a feeling of the extremely simple API and install from nuget. Check out the API documentation at NuDoq.

Read about the announcement at kzu's blog. Get some background on the state of mock libraries from Scott Hanselman.

Who?

Moq was originally developed by Clarius, Manas and InSTEDD.

Moq uses Castle DynamicProxy internally as the interception mechanism to enable mocking. It's merged into Moq binaries, so you don't need to do anything other than referencing Moq.dll, though.

Features at a glance

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 out/ref arguments

We appreciate deeply any feedback that you may have!

OhLoh

ClariusLabs

Something went wrong with that request. Please try again.