test-dotnet

You are running .NET/C# tests. This command covers Unity Test Framework (Edit Mode and Play Mode) and standard .NET testing.

Related Skills

• solana-game SKILL.md - Unity patterns, testing + PlaySolana specifics

---

TDD Workflow (6 Phases)

When developing with TDD, follow these phases strictly:

Phase 1: RED - Write Failing Test

1. Create test file in appropriate location (Tests/EditMode/ or Tests/PlayMode/)
2. Write minimal test that fails for the right reason
3. Run test to confirm it fails
4. Do NOT write production code yet

[Test]
public void Calculate_WithValidInput_ReturnsExpected()
{
    var sut = new Calculator();  // Class doesn't exist yet

    var actual = sut.Calculate(10, 2);

    Assert.That(actual, Is.EqualTo(12));
}

Phase 2: GREEN - Make Test Pass

1. Write minimal production code to pass the test
2. Only write enough code to pass - no more
3. Run test to confirm it passes
4. Commit if green

public class Calculator
{
    public int Calculate(int a, int b) => a + b;  // Minimal implementation
}

Phase 3: REFACTOR - Clean Up

1. Improve code structure without changing behavior
2. Run tests after each refactoring step
3. Keep tests green throughout
4. Apply SOLID principles, remove duplication

Phase 4: Iterate

1. Return to Phase 1 for next test case
2. Build up functionality incrementally
3. Each cycle: RED → GREEN → REFACTOR

Phase 5: Integration

1. After unit tests pass, run integration tests
2. Test component interactions
3. For Unity: run Play Mode tests

Phase 6: Review

1. Review test coverage
2. Check for missing edge cases
3. Ensure tests are maintainable
4. Remove any redundant tests

---

Core Workflow: Build → Respond → Iterate

Operate in fast, surgical development cycles with minimal token usage.

Execution Flow

1. Understand the Request: Analyze minimum code required
2. Make the Change: Implement surgical edit
3. Build: dotnet build --no-restore --nologo --verbosity minimal
4. If Build Fails: Retry once if obvious fix, then STOP and ask
5. Run Tests: dotnet test --no-build --nologo --verbosity minimal
6. If Tests Fail: Extract failures with rg, fix if obvious, else STOP and ask