You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Storybook scenarios were not exercised in CI, and there was no
self-hosted screenshot baseline for catching unintended UI changes.
This left UI regressions dependent on manual review and an external
visual testing addon.
Switch Storybook testing to a self-hosted model by wiring a dedicated
storybook test project in Vitest and adding a Playwright visual suite
that snapshots stories tagged with `visual`. The visual runner builds
and serves static Storybook output, honors optional per-story
`parameters.visual` settings, disables motion for deterministic output,
and commits an initial baseline set for stable component stories.
The CI workflow now includes an isolated Storybook/visual job that
runs story execution separately from screenshot assertions and uploads
Playwright artifacts when diffs fail. Story fixtures that depended on
current time or randomness were made deterministic so baseline images
remain stable.
This adds initial coverage for the tagged Badge, TagInput, and JSON
stories through committed Playwright snapshots, and broad story
execution coverage through the Storybook Vitest project.
0 commit comments