Write BDD-style .NET unit tests using EF Core InMemory databases and fluent builders.
npx skills add https://github.com/zlzforever/WildGoose --skill bdd-dotnet-zlzforever
Please help me install this Agent Skill. Skill: bdd-dotnet Source: https://github.com/zlzforever/WildGoose/tree/main/.claude/bdd-dotnet Command: npx skills add https://github.com/zlzforever/WildGoose --skill bdd-dotnet-zlzforever
This Skill provides a robust and maintainable framework for writing Behavior-Driven Development (BDD) style unit tests for .NET domain layers, ensuring high code quality and predictable behavior.
Use the bdd-dotnet skill to write unit tests for the CreateProduct command handler.
High-intent search queries and answers about installing and using this skill.
To write BDD unit tests for .NET domain handlers, use the Given-When-Then pattern with real repository implementations and EF Core InMemory databases. This approach creates fluent aggregate builders and fake service implementations to validate command and query handler logic predictably.
Yes, you can use EF Core InMemory databases instead of mock libraries for .NET unit testing. This approach employs real repository implementations with fake service implementations to test domain layer handlers realistically without the overhead of mocking frameworks.
The best way to structure BDD tests for .NET command and query handlers is using fluent aggregate builders with the Given-When-Then pattern. This facilitates TDD by defining clear test structures for domain logic and workflow state transitions.
To test time-dependent logic and workflow state transitions in a .NET domain, use BDD-style test structures with fake service implementations. This allows you to control time and state changes predictably while validating handler behavior through real repository implementations.
No, you do not need mocking frameworks to test .NET domain driven design handlers. This BDD testing approach replaces mock libraries with real repository implementations using EF Core InMemory and simple fake service implementations for dependencies.
You should use fluent aggregate builders in .NET BDD unit tests when you need to construct complex domain objects and test data. They provide a fluent API that makes setting up the Given state for command and query handler tests easier and more readable.
jim60105Initialize C# ASP.NET Core Web API projects with Entity Framework Core and configuration files.
askaretIdentify impacted .NET projects and update tests for minimal changes.
fpindejGenerate C# backend entities with Entity Framework Core configurations and migration commands.
nesboImplements BDD-style unit tests for .NET domain handlers using in-memory EF Core databases.
