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
This is a tracking issue the Unified UI Testing ๐ฎ project. The purpose of this issue is to keep tracking of the overall status of the project and tasks, and plan everything around it.
โ ๏ธ Problem
Storybook has the potential to be the go-to tool for comprehensive UI testing, unifying both the existing Visual Regression Testing (VRT) and Component Testing (CT) experiences. However, the current implementation falls short in two key areas:
1๏ธโฃ Fragmented workflow
As of 8.3, users begin their Storybook CT experience with Vitest via the CLI, then transition into Storybook for visual debugging. More specifically, this process includes:
Configuring the storybookScript option in the Vitest plugin.
Running vitest in watch mode from the CLI, which spawns Storybook in the background.
Viewing test failure outputs in the CLI and clicking a link to open Storybook for visual debugging.
This workflow centers on Vitest, making Storybook feel like a "sidekick" (albeit a powerful one). The constant switching between Vitest and Storybook disrupts the development flow and makes the process feel fragmented.
2๏ธโฃ Incoherent design and under-utilized CT experience
Storybook already provides a powerful VRT experience via Visual Test Addon. We have an opportunity to create a more coherent and optimized experience that fully leverages both VRT and CT capabilities within Storybook.
๐ Goals
The high-level goals of this project are:
Introduce a way to trigger test runs from the Storybook Manager UI.
Support both the Storybook Test addon (Vitest) and the Visual Test addon (Chromatic).
Support scoping down to groups, components and stories (when supported by the test provider).
Update (aggregate) story status indicators on groups, components and stories with new icons.
๐ฉ Milestones
The content you are editing has changed. Please copy your edits and refresh the page.
๐งโ๐คโ๐ง Who: @ghengeveld, @yannbf and @valentinpalkovic
This is a tracking issue the Unified UI Testing ๐ฎ project. The purpose of this issue is to keep tracking of the overall status of the project and tasks, and plan everything around it.
Storybook has the potential to be the go-to tool for comprehensive UI testing, unifying both the existing Visual Regression Testing (VRT) and Component Testing (CT) experiences. However, the current implementation falls short in two key areas:
1๏ธโฃ Fragmented workflow
As of 8.3, users begin their Storybook CT experience with Vitest via the CLI, then transition into Storybook for visual debugging. More specifically, this process includes:
storybookScript
option in the Vitest plugin.vitest
in watch mode from the CLI, which spawns Storybook in the background.This workflow centers on Vitest, making Storybook feel like a "sidekick" (albeit a powerful one). The constant switching between Vitest and Storybook disrupts the development flow and makes the process feel fragmented.
2๏ธโฃ Incoherent design and under-utilized CT experience
Storybook already provides a powerful VRT experience via Visual Test Addon. We have an opportunity to create a more coherent and optimized experience that fully leverages both VRT and CT capabilities within Storybook.
๐ Goals
The high-level goals of this project are:
๐ฉ Milestones
1. Testing module essentials
2. Discrepancy handling
3. Updating VTA
4. Static builds
5. Watch mode
6. Run individual stories
7. Enhanced story status
8. Portable stories fixes
export { A as B }
#29244Out of scope
Follow-up work
The text was updated successfully, but these errors were encountered: