unit-test-specialist

Structure unit tests using the AAA pattern (Arrange, Act, Assert) with xUnit as your test framework. Use Moq to create mock objects for dependencies, FluentAssertions for readable assertions, and organize tests across ViewModels, Services, and Repositories layers. This ensures consistent, maintainable tests aligned with .NET testing best practices.

Aim for 5-8 unit tests per public method with a 100% pass rate. Use in-memory data stores like EF Core InMemory for repository testing to achieve comprehensive coverage. Document coverage in TEST_SUMMARY.md to track progress and maintain accountability across your project layers.

Yes, FluentAssertions integrates seamlessly with xUnit. It provides fluent, readable assertion syntax that improves test clarity and maintainability. Combined with xUnit's test organization and Moq's mocking capabilities, it forms a complete testing framework for .NET projects.

Use Moq to create mock objects that simulate dependencies for isolation testing. Set up mock behavior in the Arrange phase, invoke methods in the Act phase, and verify interactions in the Assert phase. This enables focused testing of individual components without external dependencies.

Test repositories using EF Core InMemory to simulate database interactions without external dependencies. For services, inject mocked repositories and other dependencies via constructor injection, then verify behavior through assertions and mock verification. This keeps tests fast and isolated.

Yes, maintain TEST_SUMMARY.md documentation that tracks test coverage, naming conventions, and organizational structure. Clear documentation ensures team alignment, helps onboard new developers, and provides visibility into test quality and coverage across project layers.