csharp-nunit

Your goal is to help me write effective unit tests with NUnit, covering both standard and data-driven testing approaches. - Use a separate test project with naming convention [ProjectName].Tests - Reference Microsoft.NET.Test.Sdk, NUnit, and NUnit3TestAdapter 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 - Apply [TestFixture] attribute to test classes - Use [Test] attribute for test methods - Follow the Arrange-Act-Assert (AAA) pattern - Name tests using the pattern MethodName_Scenario_ExpectedBehavior - Use [SetUp] and [TearDown] for per-test setup and teardown - Use [OneTimeSetUp] and [OneTimeTearDown] for per-class setup and teardown - Use [SetUpFixture] for assembly-level setup and teardown - 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 [TestCase] for inline test data - Use [TestCaseSource] for programmatically generated test data - Use [Values] for simple parameter combinations - Use [ValueSource] for property or method-based data sources - Use [Random] for random numeric test values - Use [Range] for...