Skip to content

E01 · F09 · VAL-006 — Validate F09 ​

Replay every acceptance criterion of F09 in the playground.

Acceptance criteria ​

  • Given the playground, when each reference case of F09 is entered, then the drawing matches the expected values.
  • Given the demo page, when the Product Owner follows its guided test, then each step is ticked or commented, and misunderstandings become backlog items (ADR-0023).
  • Given the review, when the Product Owner validates, then F09 is done.

Tasks ​

One task = one commit, referenced as VAL-006.Tn. This story is not merged automatically (ADR-0028).

Tests per criterion (2026-10-11) ​

Written with the stories and the audit; counted at the validation ([F09.ACn] in test titles).

CriterionTestsWhere
F09.AC1 — rectangle tool makes a free shape2is-valid-free-shape, free-shape-corners; and every F01 and F03 rectangle test, now run through it
F09.AC2 — width and height stretch, top-left fixed5stretch-to-size (two properties), free-shape-corners
F09.AC3 — stretching without loss3stretch-to-size, free-shape-corners, playground (rectangle-free-shape)
F09.AC4 — the playground rectangle unchanged3playground (rectangle-free-shape)

Validation (2026-10-11) ​

The Product Owner tested the feature branch from the US-017 card, before the guided test was written: width, height and the points of the rectangle work as they meant; the polygon, a shape of its own, rightly behaves differently; the effective radius shown is useful. They closed the feature.

Compared with what the feature meant to show: the free shape, its stretch and its size 0 were seen as meant. The guided test of F09 (steps 34 to 38) was added afterwards. Remarks:

RemarkWhere it goes
Radii kept apart from their points: store a point with its radius (a corner)Q27 and F08, with the other changes of the model
A domain-modelling expert agent for business objectsimprovement log, RET-001