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
We use Storybook for executing screenshot tests, mostly for components in various states but also for some pages (which we will remove some time in the future). We do not need any other feature of Storybook.
However, Storybook maintenance cost is very high. They constantly break the APIs and require complex migrations, they bring dirty dependencies into the project.
Goals
Get rid of Storybook, preserving screenshot tests for components:
We do not need fancy navigation. In the worst case, a single "contents" page with links to all "stories" would be sufficient.
Potentially, we can use https://vitejs.dev/guide/build.html#multi-page-app support. However, it is not clear if the build output can be clear in this case, as we do not want to bring this tests compiled frontend into Production code.
We then can replace obscure infrastructure waitFor* helpers with standard Playwright lookups/assertions.
The text was updated successfully, but these errors were encountered:
What we have
We use Storybook for executing screenshot tests, mostly for components in various states but also for some pages (which we will remove some time in the future). We do not need any other feature of Storybook.
However, Storybook maintenance cost is very high. They constantly break the APIs and require complex migrations, they bring dirty dependencies into the project.
Goals
Get rid of Storybook, preserving screenshot tests for components:
waitFor*
helpers with standard Playwright lookups/assertions.The text was updated successfully, but these errors were encountered: