The screenshot harness cannot reach a page's interaction states #118

New Issue

2026-09-21T07:18:35Z

cgalo5758 commented

2026-09-21 07:18:35 +00:00

What a contributor runs into

The capture harness visits each route and shoots it in generic states: as it arrives, with every disclosure opened, and with an invalid submission. It has no hook to perform a sequence of acts first. So a surface whose interesting states exist only after a click, such as a table row being edited, a staged change awaiting review, a tray holding one change and then several, or the page just after a batch is applied, is captured by hand at both widths into a sheet and reviewed by eye.

Why it costs

Hand captures are not a baseline. Nothing re-shoots them on the next change, so nothing diffs them, and the review depends on someone remembering which states mattered. Every stateful surface pays this again, and the surfaces with the most states are the ones most worth watching.

Where

test/e2e/screens.

Done when

A screen can declare a sequence of acts against the page's declared form, replayed before the capture; the states reached that way are named, captured at both widths and diffed like every other state; and the surfaces currently captured by hand are covered by it.

Migrated from status/issues.md at b7a0e15

## What a contributor runs into The capture harness visits each route and shoots it in generic states: as it arrives, with every disclosure opened, and with an invalid submission. It has no hook to perform a sequence of acts first. So a surface whose interesting states exist only after a click, such as a table row being edited, a staged change awaiting review, a tray holding one change and then several, or the page just after a batch is applied, is captured by hand at both widths into a sheet and reviewed by eye. ## Why it costs Hand captures are not a baseline. Nothing re-shoots them on the next change, so nothing diffs them, and the review depends on someone remembering which states mattered. Every stateful surface pays this again, and the surfaces with the most states are the ones most worth watching. ## Where [`test/e2e/screens`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/test/e2e/screens). ## Done when A screen can declare a sequence of acts against the page's declared form, replayed before the capture; the states reached that way are named, captured at both widths and diffed like every other state; and the surfaces currently captured by hand are covered by it. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

debt

area/testing labels 2026-09-21 07:18:35 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#118