Top 20 NuGet Unit Testing Packages

AssertJ style fluent assertions for .NET unit testing frameworks.

Traced Test Extension (TTE) is an extension to major testing frameworks. It extends their capabilities to record and assert the events provided by Event Tracing for Windows (ETW).

Traced Test Extension (TTE) is an extension to major testing frameworks. It extends their capabilities to record and assert the events provided by Event Tracing for Windows (ETW).

Implementation for automated testing using Xunit and AspNetCore

Implementation for automated testing using Xunit

XUnit extensions to aid testing ASP.Net Core-specific properties / attributes etc.

Implementation for automated testing using Xunit

Mocklis is a library and source code generator for .net, targeted at generating test doubles from interfaces. This is a meta-package referencing both the library and the code generator.

This library contains some test helpers which we regularly use in our test projects.

A library for creating Behavioral-Driven (Given-When-Then) tests for MicroServices built with the Kingo.MicroServices package.

Easy to use, small, SignalR Core unit testing support with xUnit and Moq. Check my github for NUnit or MSTest version.

Implementation for automated testing using Xunit and AspNetCore

Implementation for automated testing using Xunit

Tesults NUnit library for uploading test results data to Tesults from NUnit 3 tests.

Simple and fluent web automation - Make it so easy to write a range of tests from functional, smoke to acceptance tests for your web application that there's no excuse not to.

This .NET Core library provides wrapper interfaces for the classes HttpContext, HttpRequest and HttpResponse.

xUnit Custom adapter for SpecFlow that allows running scenarios without code generation.

Reposify EF Core implementation.

Auto Health Check integration for Raygun.

Breakdance is a testing framework for managing the dangerous dance of shipping public APIs. This package in particular helps generate API reports for OData APIs, and compare them against a prior unit test run. That way, if something in the API surface changed, the unit test will fail.