Description
AutoMoqer is an "auto-mocking" container that creates objects for you. Just tell it what class to create and it will create it.
AutoMoq alternatives and similar packages
Based on the "Testing" category.
Alternatively, view AutoMoq alternatives based on common mentions on social networks and blogs.
-
Bogus
:card_index: A simple fake data generator for C#, F#, and VB.NET. Based on and ported from the famed faker.js. -
xUnit
xUnit.net is a free, open source, community-focused unit testing tool for .NET. -
Fluent Assertions
A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.7, as well as .NET Core 2.1, .NET Core 3.0, .NET 6, .NET Standard 2.0 and 2.1. Supports the unit test frameworks MSTest2, NUnit3, XUnit2, MSpec, and NSpec3. -
AutoFixture
AutoFixture is an open source library for .NET designed to minimize the 'Arrange' phase of your unit tests in order to maximize maintainability. Its primary goal is to allow developers to focus on what is being tested rather than how to setup the test scenario, by making it easier to create object graphs containing test data. -
SpecFlow
#1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration -
Testcontainers
A library to support tests with throwaway instances of Docker containers for all compatible .NET Standard versions. -
Verify
Verify is a snapshot tool that simplifies the assertion of complex data models and documents. -
NBomber
Modern and flexible load testing framework for Pull and Push scenarios, designed to test any system regardless a protocol (HTTP/WebSockets/AMQP etc) or a semantic model (Pull/Push). -
WireMock.Net
WireMock.Net is a flexible product for stubbing and mocking web HTTP responses using advanced request matching and response templating. Based on the functionality from http://WireMock.org, but extended with more functionality. -
Compare-Net-Objects
What you have been waiting for :+1: Perform a deep compare of any two .NET objects using reflection. Shows the differences between the two objects. -
Machine.Specifications
Machine.Specifications is a Context/Specification framework for .NET that removes language noise and simplifies tests. -
GenFu
GenFu is a library you can use to generate realistic test data. It is composed of several property fillers that can populate commonly named properties through reflection using an internal database of values or randomly created data. You can override any of the fillers, give GenFu hints on how to fill them. -
NetArchTest
A fluent API for .Net that can enforce architectural rules in unit tests. -
Expecto
A smooth testing lib for F#. APIs made for humans! Strong testing methodologies for everyone! -
Canopy
f# web automation and testing library, built on top of Selenium (friendly to c# also) -
ArchUnitNET
A C# architecture test library to specify and assert architecture rules in C# for automated testing. -
Fine Code Coverage
Visualize unit test code coverage easily for free in Visual Studio Community Edition (and other editions too) -
NFluent
Smooth your .NET TDD experience with NFluent! NFluent is an ergonomic assertion library which aims to fluent your .NET TDD experience (based on simple Check.That() assertion statements). NFluent aims your tests to be fluent to write (with a super-duper-happy 'dot' auto-completion experience), fluent to read (i.e. as close as possible to plain English expression), but also fluent to troubleshoot, in a less-error-prone way comparing to the classical .NET test frameworks. NFluent is also directly inspired by the awesome Java FEST Fluent assertion/reflection library (http://fest.easytesting.org/) -
xBehave.net
✖ An xUnit.net extension for describing each step in a test with natural language. -
NSpec
A battle hardened testing framework for C# that's heavily inspired by Mocha and RSpec. -
SpecsFor
SpecsFor is a light-weight Behavior-Driven Development framework that focuses on ease of use for *developers* by minimizing testing friction. -
LightBDD
BDD framework allowing to create easy to read and maintain tests. -
snapshooter
Snapshooter is a snapshot testing tool for .NET Core and .NET Framework -
Xunit.Gherkin.Quick
BDD in .NET Core - using Xunit and Gherkin (compatible with both .NET Core and .NET) -
ExpressionToCode
Generates valid, readable C# from an Expression Tree. -
Moq.Contrib.HttpClient
A set of extension methods for mocking HttpClient and IHttpClientFactory with Moq. -
SimpleStubs
*SimpleStubs* is a simple mocking framework that supports Universal Windows Platform (UWP), .NET Core and .NET framework. SimpleStubs is currently developed and maintained by Microsoft BigPark Studios in Vancouver. -
NScenario
Dead simple library for annotating steps of test case scenarios. -
SecTester
SecTester is a new tool that integrates our enterprise-grade scan engine directly into your unit tests.
ONLYOFFICE Docs — document collaboration in your environment
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of AutoMoq or a related project?
Popular Comparisons
README
AutoMoq
AutoMoqer is an "auto-mocking" container that creates objects for you. Just tell it what class to create and it will create it.
But how?
It injects mocks as any undefined dependencies.
class NeatoRepository {
public NeatoRepository(ISomething something){
// ..
}
}
var mocker = new AutoMoqer();
var neatoRepository = mocker.Create<NeatoRepository>();
// but what about ISomething?
mocker.GetMock<ISomething>(); // I was injected as ISomething
But why?
Let's pretend you did not use AutoMoq and you changed your dependencies:
// I wrote this code in my tests...
var neatoRepository = new NeatoRepository(null);
// ... then I changed my class...
class NeatoRepository {
public NeatoRepository(ISomething something, ISomethingElse somethingElse){
// ..
}
}
// NOW I HAVE TO FIX ALL OTHER REFERENCES TO GET A BUILD
var neatoRepository = new NeatoRepository(null);
If you used AutoMoq, this could would always compile:
var neatoRepository = mocker.Create<NeatoRepository>();
Leaving you to just worry about how to change your logic, not your syntax.
Another Example
The dependencies injected into the class you are testing can be accessed before and/or after you call Create. Like so:
var mocker = new AutoMoqer();
mocker.GetMock<IDataDependency>()
.Setup(x => x.GetData())
.Returns("TEST DATA");
var classToTest = mocker.Resolve<ClassToTest>();
classToTest.DoSomething();
mocker.GetMock<IDependencyToCheck>()
.Setup(x=>x.CallMe("TEST"), Times.Once());
That's It
It's a simple tool, but it can save a lot of headaches.