Claude-Tools-for-Delphi: Skill for Claude Code

DUnitX testing — reference

For the red-green discipline (failing test first, confirmed red on its assertion) use /light-review-RedGreen. This skill is the structural reference: how a fixture, a fake and an integration test are shaped here.

Non-negotiables (Gabriel's rules)

• Every [Test] makes a real assertion. Keep FailsOnNoAsserts on in the runner; a zero-assertion or Assert.Pass-only test is a fake test — the exact thing /light-review-FakeTest hunts.
• No form / UI tests. Restrict DUnitX to domain and service logic. Layout lives in the .dfm/.fmx and is not unit-tested.
• Compile only via the light-compiler agent (global CLAUDE.md rule); the agent reports compile results only — launching the test EXE to read pass/fail counts is your job.
• Reuse LightSaber in the code under test before hand-rolling.
• Test project is usually UnitTesting\Tests.dproj; if none exists, do not guess a layout — ask (template: c:\AI\Claude Code\TEMPLATE FOLDER\UnitTesting (TEMPLATE)\).

Fixture skeleton

type
  [TestFixture]
  TCustomerServiceTest = class
  private
    FService: TCustomerService;
    FRepo: TMemoryCustomerRepository;   // concrete fake, see below
  public
    [Setup]    procedure Setup;
    [TearDown] procedure TearDown;
    [Test]     procedure Create_WithValidData_Succeeds;
    [Test]     procedure Create_WithEmptyName_RaisesValidation;
  end;

procedure TCustomerServiceTest.Setup;
begin
  FRepo := TMemoryCustomerRepository.Create;
  FService := TCustomerService.Create(FRepo);
end;

procedure TCustomerServiceTest.TearDown;
begin
  FService.Free;
  FRepo.Free;
end;

Register the fixture: initialization TDUnitX.RegisterTestFixture(TCustomerServiceTest);

Naming: Method_Scenario_ExpectedBehavior