Using AutoFixture and Bogus to keep tests expressive
AutoFixture composes the test context. Bogus makes generated data easier to describe.
Posts tagged with 'nunit'
Back to all tags ←Using AutoFixture to keep unit tests focused on the scenario
A unit test should show what makes its scenario special. AutoFixture can provide a valid context by default so the Arrange phase only needs to describe the difference.
Testing ASP.NET Core endpoints with fake JWT tokens and WebApplicationFactory
Bypassing JWT validation in .NET integration tests with custom tokens and a test-only authentication setup.
Testing ASP.NET Core endpoints that use Entity Framework Core
Testcontainers and Respawn can make testing ASP.NET Core endpoints using Entity Framework Core easier and more reliable.
Reliably testing components that use Entity Framework Core
Reliably testing components using Entity Framework Core can be quite problematic. Targeting a real database comes with its own challenges. Let’s solve that!
Leveraging generic attributes to get test-specific test data
Tailoring AutoFixture’s customizations to the need of each test can cause a lot of code to be repeated. Let’s avoid that by using generic attributes.
Testing ASP.NET Core GRPC applications with WebApplicationFactory
The WebApplicationFactory can be used to create an instance of an ASP.NET Core application hosted within the test process and execute all the tests against it. We will use it to test GRPC services.
Testing ASP.NET Core web applications with WebApplicationFactory
The WebApplicationFactory can be used to create an instance of an ASP.NET Core application hosted within the test process and execute all the tests against it.
Better Moq expressions with NUnit constraints
NUnit constraints can be used when verifying invocations in Moq to create powerful and clear expressions.