csharp-xunit

Topics in the source

• XUnit Best Practices
• Project Setup
• Test Structure
• Standard Tests
• Data-Driven Tests
• Assertions
• Mocking and Isolation
• Test Organization

Your goal is to help me write effective unit tests with XUnit, covering both standard and data-driven testing approaches. Use a separate test project with naming convention [ProjectName].Tests Reference Microsoft.NET.Test.Sdk, xunit, and xunit.runner.visualstudio packages Create test classes that match the classes being tested (e.g., CalculatorTests for Calculator) Use .NET SDK test commands: dotnet test for running tests No test class attributes required (unlike MSTest/NUnit) Use fact-based tests with [Fact] attribute for simple tests Follow the Arrange-Act-Assert (AAA) pattern Name tests using the pattern MethodNameScenarioExpectedBehavior Use constructor for setup and IDisposable.Dispose() for teardown Use IClassFixture for shared context between tests in a class Use ICollectionFixture for shared context between multiple test classes Keep tests focused on a single behavior Avoid testing multiple behaviors in one test method Use clear assertions that express intent Include only the assertions needed to verify the test case Make tests independent and idempotent (can run in any order) Avoid test interdependencies Use [Theory] combined with data source attributes Use [InlineData] fo

This is an excerpt. Refer to the complete source and its current requirements.