write-unit-tests

You can generate NUnit unit tests for C# .NET projects automatically by applying the Skill to your classes, which creates comprehensive test files covering happy paths, edge cases, and error handling using AAA structure and mocks.

Yes, this unit test generation approach supports Dataverse plugins by utilizing FakeXrmEasy for mocking, alongside FakeItEasy for standard domain and infrastructure repository tests in your C# .NET codebase.

The AAA structure in generated C# unit tests stands for Arrange, Act, and Assert, organizing test code to set up data, execute methods, and verify outcomes for domain services and infrastructure repositories.

Yes, you can use this to add test coverage to an existing C# codebase by generating test files that follow project-specific patterns, including test data builders and verification helpers for consistent testing standards.

Yes, you need NUnit, FakeItEasy, and FakeXrmEasy installed in your .NET project environment, as the generated unit tests rely on these frameworks for mocking dependencies and structuring assertions.

The best way to write unit tests for domain services and infrastructure repositories in .NET is to generate them using project-specific patterns with FakeItEasy mocks, ensuring coverage of validation, edge cases, and error handling.