test(ui): record the field row's goldens #212
No reviewers
Labels
No labels
adr
android
area/calendar
area/design-system
area/i18n
area/jobs
area/offline
area/server
area/testing
bug
ci
duplicate
enhancement
help wanted
invalid
notifications
question
reliability
security
severity/low
severity/medium
tracking
web
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
eagraiclainne/app!212
Loading…
Reference in a new issue
No description provided.
Delete branch "test/field-row-goldens"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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>.pnggrammar,so
cmd/uigallerypairs them side by side.🤖 Generated with Claude Code
Test report
Coverage: 27.0%
Updated by the check workflow · commit
a4f32ace5cAndroid test report
Coverage: 10.0% of lines
Updated by the android workflow · commit
a4f32ace5cClosing: the split was wrong for a new component.
CI proved it — this branch was green and #211 was red on
check / webandandroid / build. The web job runsnpm run test:screensand the android jobruns
verifyRoborazziDebug, so the commit that adds 54 new gallery cases persurface 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.
Pull request closed