Using BenchmarkDotNet to compare .NET Core mocking library performance

This repo contains the code for -- and results of -- a series of benchmarks around the functionality of some of .NET Core's mocking libraries.

The baseline is a simple stub.

• FakeItEasy
• Moq
• NSubstitute
• Rocks

Want to add more? PRs welcome! Just add a method to IMockingBenchmark and IMockingBenchmark, implement it in each of the benchmarks, and add it to the BenchmarkTestHelpers methods.

These tests cover standard mocking framework functionality

Each test (other than construction, obviously) also has an "Only" version, where the mock is setup in the constructor, and only the method call itself is measured.

This is more accurate when comparing against larger testing classes, where you have a fixture- or assembly-level setup, that doesn't get run with every test.

Note that FakeItEasy fails all of these tests, its time growing linearly with each iteration over the method. This may be due to a FakeItEasy memory leak.

Want to add more? PRs welcome! Just add a new class implementing IMockingBenchmark or IMockingBenchmark depending on what you're testing.

This test simply creates an IThingy object to test using the given framework

A mock object is created, a method setup with a callback, and that method called

A mock object is created, with no method setup, and a void method called

A mock object is created, with no method setup, and an int method called

A mock object is created, a method setup with a return, and that method called

Verifies that the method was called

The creation of the mock object and its method setup are done outside the benchmark; only the method's call itself is tested

The creation of the mock object is done outside the benchmark; only an empty method call itself is tested

The creation of the mock object is done outside the benchmark; only an empty method itself is tested

The creation of the mock object and its method setup are done outside the benchmark; only the method's call itself is tested

The creation of the mock object and its method call are done outside the benchmark; only the verification itself is tested