Visual Studio 2022+ Test Explorer runner for the xUnit.net framework. Capable of running xUnit.net v1, v2, and v3 tests. Supports .NET 4.7.2 or later, and .NET 8 or later.
In-process console runner for xUnit.net framework, providing the entrypoint for self-executing unit tests. Supports .NET Framework 4.7.2 or later, and .NET 8 or later.
Console runner for the xUnit.net framework. Capable of running xUnit.net v1.9.2 and v2.0+ tests. Supports .NET 4.5.2 or later, .NET Core 1.x, and .NET Core 2.x.
This package includes the nunit3-console runner and test engine for version 3 of the NUnit unit-testing framework. The following extensions are included with this package: * NUnitProjectLoader - loads tests from NUnit projects * VSProjectLoader - loads tests from Visual Studio projects * NUnitV2ResultWriter - saves results in NUnit V2 format. * NUnitV2FrameworkDriver - runs NUnit V2 tests. * TeamCityEventListener - supports special progress messages used by teamcity. Other extensions, if needed, must be installed separately.
Includes the version-independent runner for xUnit.net to run both v1.9.2 and v2.0+ tests (xunit.runner.utility.*.dll). Supports .NET 3.5, .NET 4.5.2 or later, .NET Standard 1.1, .NET Standard 1.5, and .NET Core 1.0 or later.
This package is now obsolete and has been replaced by the NUnit.Console package. It includes the nunit3-console runner and test engine for version 3 of the NUnit unit-testing framework. The following extensions are included with this package: * NUnitProjectLoader - loads tests from NUnit projects * VSProjectLoader - loads tests from Visual Studio projects * NUnitV2ResultWriter - saves results in NUnit V2 format. * NUnitV2FrameworkDriver - runs NUnit V2 tests. * TeamCityEventListener - supports special progress messages used by teamcity. Other extensions, if needed, must be installed separately.
dotMemory Unit is an additional unit testing framework that allows you to write tests that check code for all kinds of memory issues. For example, these can be tests that determine leaks by checking memory for objects of a particular type, or tests that track memory traffic and fail in case the traffic exceeds some threshold. In other words, dotMemory Unit extends your unit testing framework (NUnit, MSTest, or other) with the functionality of a memory profiler. To run tests that use dotMemory Unit, you should reference the dotMemory.Unit assembly (which is a part of this package) from your test project. Tests with the support for dotMemory Unit can be run either with a standalone unit test runner of your choice or with the ReSharper unit test runner. For standalone runners, you should use a mediator - the standalone dotMemory Unit launcher. If you want to use the ReSharper unit test runner, you should have either ReSharper 9.1 (or later) or dotCover 3.1 (or later) installed on your machine
Mongo2Go is a managed wrapper around MongoDB binaries. It targets .NET Framework 4.7.2 and .NET Standard 2.1. This Nuget package contains the executables of mongod, mongoimport and mongoexport v8.0.26 for Windows (x64), Linux (x64 and arm64) and macOS (x64 and arm64). Mongo2Go has two use cases: 1. Providing multiple, temporary and isolated MongoDB databases for integration tests 2. Providing a quick to set up MongoDB database for a local developer environment
NUnitLite provides a simple way to run NUnit tests, without the overhead of a full NUnit installation. It is suitable for projects that want to have a quick way to run tests using a console runner and don't need all the features of the NUnit engine and console runner. Supported platforms: - .NET Framework 4.6.2+ - .NET 8.0+ - .NET 10.0+ How to use this package: 1. Create a console application for your tests and delete the generated class containing Main(). 2. Install the NUnitLite package, which creates a new Main() as well as adding a reference to NUnitLite. This will also bring in the NUnit package, which adds a reference to the NUnit framework to your project. 3. Add your tests to the test project and simply start the project to execute them.
Chutzpah is an open source JavaScript test runner which helps you integrate JavaScript unit testing into your website. It enables you to run JavaScript unit tests from the command line and from inside of Visual Studio. It also supports running in the TeamCity continuous integration server.
Includes runner reporters for TeamCity, AppVeyor, Verbose and Quiet output for test runners. Supports .NET 4.5.2 or later, .NET Standard 1.1, .NET Standard 1.5, and .NET Core 1.0 or later.
SpecFlow+Runner - supports SpecRun.SpecFlow and SpecRun.NUnit packages.
MSBuild runner for the xUnit.net framework. Capable of running xUnit.net v1.9.2 and v2.0+ tests. Supports .NET 4.5.2 or later.
ReportUnit is a report generator for the test-runner family. It uses stock reports from NUnit, MSTest, xUnit, TestNG and Gallio and converts them HTML reports with dashboards.
Combined package to setup SpecFlow with NUnit easily for running the tests with the NUnit runners.
SpecFlow+Runner - a smarter integration test runner for SpecFlow. Check the details on the website.
The Should Assertion Library provides a set of extension methods for test assertions for AAA and BDD style tests. It provides assertions only, and as a result it is test runner agnostic. The assertions are a direct fork of the xUnit test assertions. This project was born because test runners Should be independent of the assertions!
Machine.Specifications (MSpec) adapter for .NET Framework and .NET Core including dotnet cli (dotnet test), Visual Studio IDE, TFS, Visual Studio Online, Visual Studio Team Services.
Includes the version-independent runner for xUnit.net to run all of v1, v2, and v3 tests (xunit.v3.runner.utility.*.dll). Supports .NET Framework 4.7.2 or later, and .NET 8 or later.
SpecFlow+Runner - a smarter integration test runner for SpecFlow. Check the details on the website.
Console runner for the Context/Specification framework Machine.Specifications
This package is a fork of the xUnit.net Visual Studio runner. It contains all of the original functionality with the addition of enhanced test display names as described in PR 828 (https://github.com/xunit/xunit/pull/828) and proposed in Issue 759 (https://github.com/xunit/xunit/issues/759). The possible options are defined in the new TestMethodDisplayOptions enumeration. To enable all enhanced display name options, you must add the "xunit.methodDisplayOptions" application setting with the value "all". The class and method name options are still controlled by the TestMethodDisplay enumeration and the "xunit.methodDisplay" application setting. Visual Studio 2012+ Test Explorer runner for the xUnit.net framework. Capable of running xUnit.net v1.9.2 and v2.0+ tests. Supports .NET 2.0 or later, .NET Core 1.0 or later, and Universal Windows 10.0 or later.
Test runner for ReSharper/Rider compiled for .NETFramework and .NETCore
Console runner for the xUnit.net framework. Capable of running xUnit.net v1, v2, and v3 tests. Requires .NET Framework 4.7.2 or later.
DTO classes for MSTest adapter for ReSharper Test Runner
DTO classes for XUnit adapter for ReSharper Test Runner
NUnit features a fluent assert syntax, parameterized, generic and theory tests and is user-extensible. A number of runners, both from the NUnit project and by third parties, are able to execute NUnit tests. Version 2.6 is the seventh major release of this well-known and well-tested programming tool. This package includes the NUnit console, gui and pnunit runners and is compatible with all NUnit framework versions 2.0 through 2.6. The NUnit project editor is also included. This unofficial package is limited to run on the 4.x framework which improves compatibility with Mono when running tests compiled for 4.x.
.NET Core console runner, as a linkable library, for runner authors. For running tests, please use xunit.runner.console instead.
Now with .NET Standard support! The Should Assertion Library provides a set of extension methods for test assertions for AAA and BDD style tests. It provides assertions only, and as a result it is test runner agnostic. The assertions are a direct fork of the xUnit test assertions. This project was born because test runners Should be independent of the assertions!
Includes support for running xUnit.net v2 tests on iOS, Android, and UWP devices
UWP runner for ReSharper Test Runner
UWP runner for ReSharper Test Runner
SpecFlow+Runner - a smarter integration test runner for SpecFlow. Check the details on the website.
*TestBase* gives you a flying start with - fluent assertions that are easy to extend - sharp error messages - tools to help you test with “heavyweight” dependencies on - AspNetCore.Mvc, AspNet.Mvc or WebApi Contexts - HttpClient - Ado.Net - Streams & Logging - Mix & match with your favourite test runners & assertions. ``` UnitUnderTest.Method() .ShouldNotBeNull() .ShouldEqualByValueExceptFor(new {Id=1, Descr=expected}, ignoreList ) .Payload .ShouldMatchIgnoringCase("I expected this") .Should(someOtherPredicate); .Items .ShouldAll(predicate) .ShouldContain(item) .ShouldNotContain(predicate) .Where(predicate) .SingleOrAssertFail() item .ShouldEqualByValue() .ShouldEqualByValueExceptFor(...) .ShouldEqualByValueOnMembers() string .ShouldMatch(pattern) .ShouldNotMatch() .ShouldBeEmpty() .ShouldNotBeEmpty() .ShouldNotBeNullOrEmptyOrWhiteSpace() .ShouldEqualIgnoringCase() .ShouldContain() .ShouldBeContainedIn() .ShouldStartWith() .ShouldEndWith() ... numeric .ShouldBeBetween() .ShouldEqualWithTolerance()....GreaterThan....LessThan...GreaterOrEqualTo ... ienumerable .ShouldAll() .ShouldContain() .ShouldNotContain() .ShouldBeEmpty() .ShouldNotBeEmpty() ... stream .ShouldHaveSameStreamContentAs() .ShouldContain() value .ShouldBe() .ShouldNotBe() .ShouldBeOfType() .ShouldBeAssignableTo() ... ``` Testable Logging is in packages Extensions.Logging.ListOfString and Serilog.Sinks.ListOfString ``` // Extensions.Logging.ListOfString var log = new List<String>(); ILogger mslogger= new LoggerFactory().AddStringListLogger(log).CreateLogger("Test2"); // Serilog.Sinks.ListOfString Serilog.Logger slogger= new LoggerConfiguration().WriteTo.StringList(log).CreateLogger(); ```
The Should Assertion Library provides a set of extension methods for test assertions for AAA and BDD style tests. It provides assertions only, and as a result it is test runner agnostic. The assertions are a direct fork of the xUnit test assertions. This project was born because test runners Should be independent of the assertions!
Grunt is the JavaScript task runner, which main purpose is to automate repetitive tasks like minification, compilation, unit testing, linting, etc. With literally thousands of plugins to choose from, you can use Grunt to automate just about anything with a minimum of effort.
The TAP support for the Cake.Issues addin for Cake allows you to read Test Anything Protocol (TAP) compatible files. This addin provides the aliases for reading issues from TAP compatible files and providing them to the Cake.Issues addin. It also requires the core Cake.Issues addin. There are also additional addins for generating reports or posting issues to pull requests. See the Project Site for an overview of the whole ecosystem of addins for working with issues in Cake scripts. NOTE: This is the version of the addin compatible with Cake Frosting. For addin compatible with Cake Script Runners see Cake.Issues.Tap.