Task: Test the engine settings
Table of Contents
This page documents a task in the See and change everything a report runs story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
A person runs the engine settings scenario against a live environment and records each step as passed or failed.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | See and change everything a report runs |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-23 |
3. Acceptance
- The scenario ran end to end on a rebuilt environment.
- Every failed step has a captured defect.
4. Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
5. Measurements
Every number this task claims about a tree, with the command that produced it
and the commit it was measured at. A number without both is not a measurement,
because a clean-up record describes a tree and trunk moves under a branch: a
consumer count, a gate's component count and a suite's size all change with no
code changing, and the reader of a bare number cannot tell which tree it came
from. Where the raw output matters, put it in an evidence/ file beside the
task and name that file in the Command column.
| What | Value | Command | Commit |
|---|---|---|---|
6. Notes
7. Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario)
that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
| Walk the engine settings screens as an Acme user | FAILED | Ran on 2026-10-23 as the tenant administrator at the group party. 7 steps passed and 6 failed. Four failures have one cause: a row of a child party cannot be changed or read in history from the group party. One failure was a wrong expectation about the list, and one was a missing language selector. The follow-up tasks of the story cover each. |
8. PRs
9. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
10. Result
The scenario ran once in the browser, as the tenant administrator at the group party, and once for a senior trader. Seven of 13 steps passed. Six failed: four from one defect (a row of a child party cannot be changed or read in history from the group party), one from a wrong expectation about the list, and one because the app has no language selector. A walk of the same operations through the API from a UK session passed. Each failure has a follow-up task in the story. The task is done because the scenario ran and every failure is captured; the story stays open for the follow-up tasks.