What problem does it solve? Developers migrating from xUnit or NUnit to TUnit often struggle with its different attribute model, asynchronous fluent assertions, and lifecycle hooks, leading to inconsistent or incorrect test code. ## Core Features & Use Cases - TUnit Test Authoring: Provides conventions for test structure, naming, AAA pattern, and lifecycle hooks like [Before(Test)] and [After(Class)]. - Data-Driven Testing: Covers [Arguments], [MethodData], [ClassData], and custom ITestDataSource implementations for parameterized tests. - Fluent Assertions: Guides usage of await Assert.That() with chaining via .And, .Or, and .Within for expressive validation. - xUnit Migration: Maps xUnit constructs ([Fact], [Theory], [InlineData], IClassFixture) to their TUnit equivalents. - Use Case: When refactoring an existing xUnit test suite to TUnit, apply the migration mappings to convert attributes and assertions while adopting parallel execution controls like [NotInParallel] and [ParallelLimit<T>]. ## Quick Start Help me write a TUnit data-driven test class for my Calculator service using [Arguments] and fluent assertions.