Release 0.1.154
Each scenario now has a Proof button that shows why it works — the screens, the data it changed and everything the app did along the way — so you can accept a feature without reading its code. Prototypes are checked against the legacy app's screens, and the Domain diagram stays readable on large models.
Upgrade notes
- Three database migrations run on upgrade. They only add new data; nothing existing is changed.
- No changes to
.envordocker-compose.yml.
New
Proof for every scenario. Once a run has tested a scenario, its Proof button opens a dialog with Evidence and Test Replay; its icon shows whether the scenario is proven, differs from the legacy app, or failed. What the test run recorded shows the screen after each step, the rows the scenario changed in the database, and an Activity table of every API call, SQL statement, call out to another system, message and file, step by step. Click an API call to see the SQL it ran and what it called. A Scenario Outline shows each example's own proof. Under Added by the agent, the agent adds only what a recording cannot show, such as the legacy screen beside the new one. Tick Reviewed on what you accept, or Report issue to file a bug report. SQL is recorded for Postgres and SQL Server projects; passwords, tokens and session cookies are never shown.
Prototypes checked against the legacy screens. After a feature with legacy screens is built, another agent compares each state with its legacy screen. A difference nobody asked for goes back to be fixed, and the feature's Stories or Prototype view says whether the stories match or which differences remain. To get a new design instead, say so in the instructions box; when the check cannot tell what you meant, it asks you once.
Improvements
- The Diagram view on the Domain page opens on one box per subdomain. Click a subdomain to see its aggregates, and an aggregate to see its neighbours, with each arrow labelled by the attributes that make the reference. The breadcrumb goes back.
- Test Replay of an API scenario now shows each HTTP call the scenario made.
- In a module, each member's prototype is built by an agent of its own, so the last member gets the same care as the first.
Fixes
- Since 0.1.153, agent runs that were offered the legacy app or its screens failed before they started.