NUnit
AutoFixture
NUnit | AutoFixture | |
---|---|---|
26 | 11 | |
2,467 | 3,259 | |
0.3% | 1.2% | |
9.1 | 4.6 | |
6 days ago | about 2 months ago | |
C# | C# | |
MIT License | 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.
NUnit
-
CI/CD Pipeline Using GitHub Actions: Automate Software Delivery
.NET / xUnit / NUnit / MSTest
-
Fluent Assertions: Fluently Assert the Result of .NET Tests
This library extends the traditional assertions provided by frameworks like MSTest, NUnit, or XUnit by offering a more extensive set of extension methods. Fluent Assertions supports a wide range of types like collections, strings, and objects and even allows for more advanced assertions like throwing exceptions.
-
TDD vs BDD - A Detailed Guide
Next, you need to install a testing framework that will be used for performing unit testing in your project. Several testing frameworks are available depending on the programming language used to create an application. For example, JUnit is commonly used for Java apps, pytest for Python apps, NUnit for .NET apps, Jest for JavaScript apps, and so on. We’ll use the Jest framework for this tutorial since we are using JavaScript.
-
Setting up a simple testing project with C#
At this point you're going to see a familiar screen asking you to select a project. Here we're looking for a test project. By default, Visual Studio gives you access to 3 different testing frameworks based on your choice of project. These are MSTest, XUnit and NUnit. Ultimately, all 3 of these testing accomplish the same thing, and I've worked with all of them at various points in my career. The difference is mainly in exact syntax and documentation. Although, it's generally considered that MSTest is a little "older" than NUnit or XUnit, so I tend to see it less now. For the purposes of this demo, I'm going to go with NUnit:
-
Test-Driven Development
Use a testing framework: Utilize a testing framework like NUnit, xUnit, or MSTest to create, organize, and run your tests. These frameworks provide a consistent way to write tests, generate test reports, and integrate with continuous integration tools.
-
Debugging extension for test library
So I wrote extension attribute for Nunit, the opposite of how the retry attribute works.
- 2023 Development Tool Map
-
Unlock the Power of Unit Testing: A Beginner’s Guide to Quality Software Development
This is a basic example of how to create an NUnit unit test for a simple API in a controller with C#. You can find more information and resources on the NUnit website and in the NUnit documentation.
-
Commemorating Charlie Poole's Contributions to the NUnit Project
Has #NUnit helped you, your career, or your organization? We'd love for you to tell that story here, to celebrate Charlie: https://github.com/nunit/nunit/discussions/4283
After over TWENTY years leading the NUnit project, Charlie is stepping back.
Has NUnit helped you, your career, or your organization? We'd love to hear about it at https://github.com/nunit/nunit/discussions/4283.
> To attempt to quantify Charlie’s contributions to NUnit is a daunting task. He was the lead of NUnit across at least 207 releases in 37 different repositories, authoring 4,898 commits across them. He participated in 2,990 issues, 1,305 PRs, and impacted 6,992,983 lines of code. And those are only the ones we can easily find; our numbers are sourced from after NUnit moved the project to GitHub in 2011, which means there are at least 9 additional years of work not quantified above.
I think of Charlie as one of the ".NET OSS OGs". I'd love to see him celebrated.
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.
NSubstitute - A friendly substitute for .NET mocking libraries.
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.
FakeItEasy - The easy mocking library for .NET
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
Shouldly - Should testing for .NET—the way assertions should be!
NBuilder - Rapid generation of test objects in .NET
coverlet - Cross platform code coverage for .NET [Moved to: https://github.com/coverlet-coverage/coverlet]
FsCheck - Random Testing for .NET