csharp-tunit

Best practices for writing unit tests with TUnit, including data-driven and advanced testing patterns. Your goal is to help me write effective unit tests with TUnit, covering both standard and data-driven testing approaches. Why TUnit over xUnit? TUnit offers a modern, fast, and flexible testing experience with advanced features not present in xUnit, such as asynchronous assertions, more refined lifecycle hooks, and improved data-driven testing capabilities. TUnit's fluent assertions provide clearer and more expressive test validation, making it especially suitable for complex .NET projects. - Use [Test] attribute for test methods; follow Arrange-Act-Assert pattern with naming convention MethodName_Scenario_ExpectedBehavior - Data-driven testing via [Arguments] , [MethodData] , and [ClassData] attributes; multiple [Arguments] can apply to the same method - Fluent async assertions with await Assert.That() syntax; chain with .And or .Or operators and use .Within() for tolerance comparisons - Lifecycle hooks at multiple scopes: [Before/After(Test)] , [Before/After(Class)] , and [Before/After(Assembly)] for flexible setup and teardown - Advanced features include [Repeat(n)] , [Retry(n)] , [Timeout] , [ParallelLimit ] , and [DependsOn] for test control; parallel execution enabled by default - Use a separate test project with naming convention [ProjectName].Tests - Reference TUnit...