Shouldly
AutoFixture
Our great sponsors
| Shouldly | AutoFixture | |
|---|---|---|
| 4 | 11 | |
| 1,970 | 3,212 | |
| 0.5% | 0.5% | |
| 6.8 | 4.9 | |
| 9 days ago | 10 days ago | |
| C# | C# | |
| GNU General Public License v3.0 or later | MIT License |
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.
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
AutoFixture
-
API: Go, .NET, Rust
Yes, it does feel like some of the "standard stuff" in other more nuanced languages are missing (especially miss AutoFixture ngl). Some of those are a conscious decison by the golang team for example.
-
Integration Testing Postgres Store
Our first test is very easy, I like to name my tests as MethodName_GivenCondition_ShouldExpectedResult to follow the pattern, I have added GetById_GivenRecordDoesNotExist_ShouldReturnNull and I am going to leavarage excellent AutoFixture to get a new Guid as parameter. For this test we don't need arrange part, we would skip to the act and then assert. For Assertion I am going to use FluentAssertions. For this test we need to assert the returned result is null.
-
Setting up a simple testing project with C#
The next test to talk about, is that if this was a bank, we would have multiple customers, who can hold multiple accounts that we need to calculate the interest for. You could manually construct these objects if you want, but I'm going to use a package called AutoFixture to make life easier.
-
AutoFixture Tips and Tricks
AutoFixture is an amazing library that simplifies the process of creating test data in .NET. If for some reason you don't use this fantastic tool, it's time to consider it. Today, I'm going to share some tips for using AutoFixture that will be beneficial for developers of all skill levels. Let's get started!
- Integration tests without API dependencies with ASP.NET Core and WireMock.Net
-
I need a C# crash course for experienced developers
AutoFixture
-
Reduce your tests cognitive complexity with AutoFixture
Ensuring that your test is still readable and not bloated by the setup of those variables may be quite a challenge but hopefully no more with AutoFixture, let's see how!
-
Practical complex data for unit testing
One neat library for creating and generating test data is AutoFixture. The creators describe it as follows:
-
14 .NET packages I always recommend
First time I heard of Bogus, looks interesting, been using AutoFixture for those will definitely take a look at it.
- LPT: There is a library called Bogus, you should know it exists much earlier than I did in my career.
What are some alternatives?
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.
Bogus - :card_index: A simple fake data generator for C#, F#, and VB.NET. Based on and ported from the famed faker.js.
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.
NSubstitute - A friendly substitute for .NET mocking libraries.
NUnit - NUnit Framework
FakeItEasy - The easy mocking library for .NET
should - Should Assertion Library
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
NBuilder - Rapid generation of test objects in .NET
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/)
FsCheck - Random Testing for .NET