Assertion

TypeScript Definitions (d.ts) for assertion-error. Generated based off the DefinitelyTyped repository [git commit: 49e00c423a63b6e5b00cf0105c5fe6a2ac57336b]. http://github.com/DefinitelyTyped

Includes the assertion library from xUnit.net (xunit.assert.dll). Supports .NET Standard 1.1+ and .NET 6.0+.

NUnit is a unit-testing framework for all .NET languages. It can run on macOS, Linux and Windows operating systems. NUnit can be used for a wide range of testing, from unit testing with TDD to full-fledged system and integration testing. It is a non-opinionated, broad and deep framework with multiple different ways to assert that your code behaves as expected. Many aspects of NUnit can be extended to suit your specific purposes. The latest version, version 4, is an upgrade from the groundbreaking NUnit 3 framework. It is a modernized version, aimed at taking advantage of the latest .NET features and C# language constructs. If you are upgrading from NUnit 3, be aware of the breaking changes (https://docs.nunit.org/articles/nunit/release-notes/breaking-changes.html#nunit-40). Please see the NUnit 4 Migration Guide (https://docs.nunit.org/articles/nunit/release-notes/Nunit4.0-MigrationGuide.html) and take care to prepare your NUnit 3 code before you do the upgrade. Supported platforms: - .NET Framework 4.6.2+ - .NET 6.0+ - .NET 8.0+

This project enhances LINQ to Objects with the following methods: Acquire, Aggregate (some EXPERIMENTAL), AggregateRight, Append, Assert, AssertCount, AtLeast, AtMost, Await (EXPERIMENTAL), AwaitCompletion (EXPERIMENTAL), Backsert, Batch, Cartesian, Choose, CountBetween, CompareCount, CountBy, CountDown, Consume, DistinctBy, Duplicates, EndsWith, EquiZip, Evaluate, Exactly, ExceptBy, Exclude, FallbackIfEmpty, FillBackward, FillForward, Flatten, Fold, ForEach, From, FullGroupJoin, FullJoin, Generate, GenerateByIndex, GroupAdjacent, Index, IndexBy, Insert, Interleave, Lag, Lead, LeftJoin, Maxima, Memoize (EXPERIMENTAL), Merge (EXPERIMENTAL), Minima, Move, OrderBy, OrderedMerge, Pad, PadStart, Pairwise, PartialSort, PartialSortBy, Partition, Permutations, Pipe, Prepend, PreScan, Random, RandomDouble, RandomSubset, Rank, RankBy, Repeat, Return, RightJoin, RunLengthEncode, Scan, ScanBy, ScanRight, Segment, Sequence, Shuffle, SkipLast, SkipLastWhile, SkipUntil, Slice, SortedMerge, Split, StartsWith, Subsets, TagFirstLast, TakeEvery, TakeLast, TakeUntil, ThenBy, ToArrayByIndex, ToDataTable, ToDelimitedString, ToDictionary, ToHashSet, ToLookup, Trace, Transpose, TraverseBreadthFirst, TraverseDepthFirst, TrySingle (EXPERIMENTAL), Unfold, Window, WindowLeft, WindowRight, ZipLongest, ZipShortest

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!

Fluent Assertions extensions for ASP.NET Core MVC.

Includes the current assertion library from xUnit.net, as source into your project. Supports any platform(s) compatible with .NET Standard 1.1.

Extension to FluentAssertions which improves the usage of OneOf to allow easier unit testing. It does this by providing extensions which fail with useful errors when OneOf like values are found and acted upon.

Bellatrix is a cross-platform, easily customizable and extendable .NET test automation framework that increases tests’ reliability.

Package Description

Advanced testing library for F#

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.

An open source utility to turn object graphs into strings. Automate your ToString and unit tests asserts.

Bellatrix is a cross-platform, easily customizable and extendable .NET test automation framework that increases tests’ reliability.

When you make a unit test assertion with PowerAssert, your assertion messages become much more useful.

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!

Description

Fluent Assertions extensions for ASP.NET MVC 5.

An extendible implementation of the Assert class in MSTest. Allows for extending the Assert methods with the default MSTest methods as a default. Includes a: * Throws() method for asserting exceptions. * ThrowsAsync() method for asserting exceptions for async methods. INSTRUCTIONS: In your test class, inherit from MsTestExtensions.BaseTest. Type Assert.Throws() or Assert.ThrowsAsync().. that's it! All of the standard Assert. methods from MsTest will still be available. Project page can be found at: https://github.com/bbraithwaite/MSTestExtensions

Fluent assertions express what you want tested instead of how. This project also provides a simple BDD framework that lets you write tests that can be easily understood and verified by non-developers.

Simple unit testing and assertion tools for use with Bam

Extension methods for asserts for a more readable assert. Ex: 1.ShouldNotBeEqualTo(2)

Assertions (Assert.That(Value.Of())

Fluent Assertions extensions for Newtonsoft.Json

Method Chaining base UnitTesting Extension Methods and Dynamic Private Accessor for MSTest. This provides only single .cs file.

.NET Unit test helpers for asserting that exceptions were / weren't thrown, and for "scenario tests".

Fluent Assertions for Microsoft.Extensions.DependencyInjection service collection

Fluent Assertions extensions for Autofac

Package Description

Fluent Assertions extensions for ASP.NET MVC 4.

Library for easy fluent assertions

A result object implementation.

Additonal FluentAssertions for multithreaded tests

HiFramework.Assert

Genesis.Ensure is a library for application authors (not library authors) that facilitates runtime expectation assertions that can be compiled out of performance-critical builds.

MvcRouteTester is a .Net library to help unit testing ASP MVC route tables. It contains asserts for for both regular controllers and the Api controllers that are new in MVC 4.0. It is built in .Net 4.5 and ASP MVC 5.2.3. See the project page for packages for ASP MVC 51, 5.0 and ASP MVC 4.0

MvcRouteTester is a .Net library to help unit testing ASP MVC route tables. It contains asserts for for both regular controllers and the Api controllers that are new in MVC 4.0. It is built in .Net 4.0 and ASP MVC 4.0.

Extension methods that provide fluent assertions on top of BUnit.

HttpClient extensions to test REST endpoints.

Expecto is a smooth test framework for F#, cloned from Fuchu with added functionality for making it easier to use.

Fluent API for asserting types and properties.

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!

Extensions for Fluent Assertions for testing Ninject bindings.

Extension to FluentAssertions which improves the usage of Discriminated Unions against standard object assertions. Intened to be a base for other Specific DU assertions to build upon

This library extends the core functionality of FluentAssertions by adding assertions on the HttpResponseMessage class. Fluent assertions quickstarts and tutorials - https://fluentassertions.com

This replaces using (sic!) AssertionScope by the Action invocation (AssertMultiple.Multiple).

Analyzers and code fixes for Gu.Roslyn.Asserts. Fixes breaking changes etc.

Unit tests will often need to assert that a sizeable amount of data matches an expectation, and this is difficult with only the traditional style of assertion. You essentially have the choice of writing a long list of simple assertions, or concatenating the output into a string and using a single assert against that. However, when these assertions fail it can be very hard to determine in what ways the output differs from the expectation. One solution to this problem is a different workflow from traditional unit testing - instead of making a prediction in the code, and then checking the output against the prediction, what if you formatted the output and displayed it side by side with the last "approved" version. This is what TestConsole.Core provides. On a build server, when the test result does not match the default behaviour is just to fail the test, whereas on a development PC you can configure the library to use an installed file compare utility to display the differences. If the differences are expected, you can copy the new result over to the approved version and the test will pass. TestConsole.Core inherits all of the formatting capabilities from the original TestConsole project, and adds test approval features. Users of ApprovalTests will recognise the workflow and the functionality, but at the time of publishing, ApprovalTests is full framework only, whereas TestConsole.Core is intended to allow testing in both full framework and .NET core test suites. I did not set out to build an alternative to ApprovalTests, but I need to be able to test netcoreapp code, and the conversion of TestConsole was not difficult. However, ApprovalTests did not support netstandard or netcoreapp test suites and I couldn't wait any longer, so I built the subset of ApprovalTests features that I needed into TestConsole.Core from scratch. As a result, the syntax is a little different to ApprovalTests, particularly where it relates to selecting a file compare tool, and also relating to what can be directly approved. The intention of the test approval features is to allow data formatted using the TestConsole Output object to be approved, and I've also extended it to handle any plain text.

Method Chaining base UnitTesting Extension Methods and Dynamic Private Accessor for NUnit. This provides only single .cs file.

Extensions and utilities for XUnit.NET test projects This includes API for making tests dynamically skippable, asserting timeouts on async tasks, and other helpful utilities. Commonly used types: McMaster.Extensions.Xunit.SkippableFact McMaster.Extensions.Xunit.SkippableTheory