Aglet

Verify Cumulative Report Reset Semantics

Cumulative verification tests the series as a sequence rather than inspecting one point. Exercise group changes, reset dates, missing periods, filters, and period boundaries. Compare expected running values with chart, table, card, and export output, and make carry-forward behavior explicit where the report permits it.

Check whether the outcome improved

  1. Define sequence assertions

    Write expected order, partition, start, reset condition, missing-period treatment, value at each row, label, and export cell. State whether the series is calendar, group, or lifetime cumulative. A pass requires the reset boundary to be discoverable by a reviewer.

  2. Exercise resets and filters

    Run two groups, reset edge, missing period, reordered input, and filtered subset fixtures through every supported surface. Compare sequence, totals, annotations, and labels. Confirm that a filter changes the intended series scope rather than only hiding earlier points.

  3. Review the running story

    Ask a reviewer to explain where the series starts, when it resets, and how a missing period affects the next value. Preserve fixture, filter state, report revision, and evidence. Record a bounded outcome when a chart is correct but omits context available in the table or export.

What to carry forward

Verification passes when cumulative values follow the documented order, partition, and reset rule across reviewed surfaces. Report a bounded pass for unsupported missing-period cases. Keep verification inconclusive when a later point depends on an invisible carryover or an export hides the reset basis.

Technical background: Metabase documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow