Xunit.Gherkin.Quick
Shouldly
| Xunit.Gherkin.Quick | Shouldly | |
|---|---|---|
| 2 | 4 | |
| 190 | 1,978 | |
| - | 0.4% | |
| 0.0 | 6.2 | |
| over 1 year ago | 10 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.
Xunit.Gherkin.Quick
-
NUnit vs XUnit for .net6+ microservices
Extensible: Has some really good extension support. There are libs that provide some very interesting ways to use xunit, such as Xunit.Gherkin.Quick, xunit-spec, xunit-bdd, CoreBDD, and many others
-
BDD-style Testing in F# with Xunit.Gherkin, GherkinProvider and TickSpec
There is a hidden gem for Xunit called Xunit.Gherkin.Quick which allows you to create standard feature files using the Gherkin language, and automate these with Xunit-based tests.
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?
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
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.
NUnit - NUnit Framework
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.
SpecsFor - SpecsFor is a light-weight Behavior-Driven Development framework that focuses on ease of use for *developers* by minimizing testing friction.
should - Should Assertion Library
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
Canopy - f# web automation and testing library, built on top of Selenium (friendly to c# also)
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/)