Our great sponsors
-
Xunit.Gherkin.Quick
BDD in .NET Core - using Xunit and Gherkin (compatible with both .NET Core and .NET)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
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
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 :)
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
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
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
Attachments: At this time you still cannot attach files to test runs, although the functionality finally is coming in V3!
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 :)