What problem does it solve? Writing consistent, maintainable unit tests in C# requires knowing XUnit's conventions for test structure, data-driven testing, assertions, and isolation, which developers often apply inconsistently across a codebase. ## Core Features & Use Cases - Test Structure Guidance: Apply the Arrange-Act-Assert pattern, [Fact] attributes, constructor setup, IDisposable teardown, and IClassFixture<T>/ICollectionFixture<T> shared contexts. - Data-Driven Testing: Build parameterized tests with [Theory] combined with [InlineData], [MemberData], [ClassData], or custom DataAttribute implementations. - Assertions and Mocking: Use the correct Assert methods for equality, collections, regex, and exceptions, and isolate units with Moq or NSubstitute. - Use Case: When adding tests for a new Calculator class, generate a CalculatorTests class in a [ProjectName].Tests project with properly named MethodName_Scenario_ExpectedBehavior tests runnable via dotnet test. ## Quick Start Write XUnit unit tests for my Calculator class using the AAA pattern, including a data-driven theory with InlineData for the Add method.