csharp-tunit

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 a separate test project with naming convention [ProjectName].Tests - Reference TUnit package and TUnit.Assertions for fluent assertions - Create test classes that match the classes being tested (e.g., CalculatorTests for Calculator ) - Use .NET SDK test commands: dotnet test for running tests - TUnit requires .NET 8.0 or higher - No test class attributes required (like xUnit/NUnit) - Use [Test] attribute for test methods (not [Fact] like xUnit) - Follow the Arrange-Act-Assert (AAA) pattern - Name tests using the pattern MethodName_Scenario_ExpectedBehavior - Use lifecycle hooks: [Before(Test)] for setup and [After(Test)] for teardown - Use [Before(Class)] and [After(Class)] for shared context between tests in a class - Use [Before(Assembly)] and [After(Assembly)] for shared context across test classes - TUnit supports advanced lifecycle hooks like [Before(TestSession)] and...