dotnet-tdd

TDD in ASP.NET Core with EF Core involves writing failing xUnit tests for API services and domain logic first, then implementing minimal production code to pass. This skill guides you through strict mock boundaries using NSubstitute to ensure real domain behavior is tested.

The best way to structure xUnit tests for .NET domain logic is to emphasize testing public behavior rather than internal getters and setters. You should use strict mock boundaries with NSubstitute and prioritize integration tests to verify actual database state and API responses.

True Test-Driven Development for EF Core requires integration tests to verify real database state and API responses. While unit tests with NSubstitute check domain logic, integration tests ensure your data access layers and API endpoints behave correctly under real conditions.

You should avoid getter and setter tests in .NET TDD because they verify trivial language mechanics rather than meaningful public behavior. True TDD focuses on testing domain logic and real outcomes through the Red-Green-Refactor cycle, ensuring robust codebases.

Yes, you can use NSubstitute with xUnit for mocking in ASP.NET Core. This TDD workflow uses NSubstitute to establish strict mock boundaries, ensuring that your xUnit tests validate real domain behavior rather than just testing the mocks themselves.

You refactor code in the TDD Refactor phase after writing a failing test and implementing just enough production code to make it pass. During this phase, you clean up the codebase while keeping all xUnit tests green, ensuring functionality remains intact.