CheckTestOutput
Shouldly
Our great sponsors
| CheckTestOutput | Shouldly | |
|---|---|---|
| 1 | 4 | |
| 0 | 1,977 | |
| - | 0.8% | |
| 4.4 | 6.2 | |
| 9 months ago | 3 days ago | |
| C# | C# | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CheckTestOutput
Shouldly
-
NUnit vs XUnit for .net6+ microservices
On a side note, something I would highly recommend NOT doing is using the built in assertion types for any of the test adapters. Without a doubt the hardest part of switching unit test frameworks is having to fix all your assertions which is why we use 3rd party assertions. The built-in assertions also tend to not be very feature rich and don't have the most helpful messages. We personally use FluentAssertions, but there are other options such as Shoudly or Should. I highly recommend picking one of them over the built in assertions. You will thank yourself later :)
-
I need a C# crash course for experienced developers
Shouldly - More "fluent" way of writing assertions that I tend to like more personally. Example:
-
What's your go-to unit testing tool?
I use NUnit and Shoudly.
-
Adelaide United's Josh Cavallo has openly come out as gay.
Robbie Rogers came out in the MLS like a decade ago
What are some alternatives?
Fine Code Coverage - Visualize unit test code coverage easily for free in Visual Studio Community Edition (and other editions too)
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.
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.
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.
NUnit - NUnit Framework
xBehave.net - ✖ An xUnit.net extension for describing each step in a test with natural language.
should - Should Assertion Library
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).
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
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
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/)