test(ui): record the field row's goldens #212

Closed
nalum wants to merge 1 commit from test/field-row-goldens into feat/field-row
Owner

The pixels for #171, kept out of the component's own diff so the change a
person has to read is 32 files of code rather than 140.

108 images, 54 per surface: nine cases on hearth in light and dark, plus
the canonical editing case across the other eighteen theme families in
both modes. Cases are the four row states, the empty note, a removed
record, and the three snackbar lines — committed, replaced-someone's-
change, and the late conflict notice.

Both surfaces follow the <component>-<case>-<family>-<mode>.png grammar,
so cmd/uigallery pairs them side by side.

🤖 Generated with Claude Code

The pixels for #171, kept out of the component's own diff so the change a person has to read is 32 files of code rather than 140. 108 images, 54 per surface: nine cases on hearth in light and dark, plus the canonical editing case across the other eighteen theme families in both modes. Cases are the four row states, the empty note, a removed record, and the three snackbar lines — committed, replaced-someone's- change, and the late conflict notice. Both surfaces follow the `<component>-<case>-<family>-<mode>.png` grammar, so `cmd/uigallery` pairs them side by side. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
test(ui): record the field row's goldens
All checks were successful
check / commits (pull_request) Successful in 8s
check / go (pull_request) Successful in 2m48s
check / report (pull_request) Successful in 3s
check / web (pull_request) Successful in 4m8s
android / build (pull_request) Successful in 6m20s
android / report (pull_request) Successful in 4s
a4f32ace5c
Both surfaces, nine cases on hearth in light and dark, and the canonical
editing case across the other eighteen families — 54 images each. Kept
apart from the component so the diff that has to be read by a person is
the code, and the diff nobody reads is the pixels.

Test report

Suite Tests Result Skipped
Unit 1434 ✅ pass 1
Integration 130 ✅ pass —

Coverage: 27.0%

Updated by the check workflow · commit a4f32ace5c

<!-- ci-test-report --> ## Test report | Suite | Tests | Result | Skipped | | --- | --: | --- | --: | | Unit | 1434 | ✅ pass | 1 | | Integration | 130 | ✅ pass | — | **Coverage:** 27.0% <sub>Updated by the check workflow · commit a4f32ace5cd7177a29b95a1cf30bd3d310f9f5ee</sub>

Android test report

Suite Tests Result Skipped
Unit (debug) 69 ✅ pass 0

Coverage: 10.0% of lines

Updated by the android workflow · commit a4f32ace5c

<!-- android-test-report --> ## Android test report | Suite | Tests | Result | Skipped | | --- | --: | --- | --: | | Unit (debug) | 69 | ✅ pass | 0 | **Coverage:** 10.0% of lines <sub>Updated by the android workflow · commit a4f32ace5cd7177a29b95a1cf30bd3d310f9f5ee</sub>
Author
Owner

Closing: the split was wrong for a new component.

CI proved it — this branch was green and #211 was red on check / web and
android / build. The web job runs npm run test:screens and the android job
runs verifyRoborazziDebug, so the commit that adds 54 new gallery cases per
surface cannot pass without the images those cases compare against.

The repo's "re-record goldens in their own commit" rule is about changing an
existing component: there the code commit still passes, because the old goldens
are already in the tree. A brand-new component has no such fallback, and
splitting it guarantees one red commit in the stack.

The goldens are folded back into #211, which keeps every commit green on its
own.

Closing: the split was wrong for a new component. CI proved it — this branch was green and #211 was red on `check / web` and `android / build`. The web job runs `npm run test:screens` and the android job runs `verifyRoborazziDebug`, so the commit that adds 54 new gallery cases per surface cannot pass without the images those cases compare against. The repo's "re-record goldens in their own commit" rule is about changing an existing component: there the code commit still passes, because the old goldens are already in the tree. A brand-new component has no such fallback, and splitting it guarantees one red commit in the stack. The goldens are folded back into #211, which keeps every commit green on its own.
nalum closed this pull request 2026-08-24 11:24:37 +00:00
All checks were successful
check / commits (pull_request) Successful in 8s
check / go (pull_request) Successful in 2m48s
check / report (pull_request) Successful in 3s
check / web (pull_request) Successful in 4m8s
android / build (pull_request) Successful in 6m20s
android / report (pull_request) Successful in 4s

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
eagraiclainne/app!212
No description provided.