Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[@storybook/addon-storyshots] Support for other test runners (vitest)
See original GitHub issueIs your feature request related to a problem? Please describe
@storybook/addon-storyshots is tied to running in a Jest environment, so in projects using other test runners it is hard to integrate.
Describe the solution you’d like
@storybook/addon-storyshots to support other test runners like Vitest.
Describe alternatives you’ve considered I tried to replace the globals Jest provides with those from Vitest, but had no luck.
Are you able to assist to bring the feature to reality? Maybe depends on what solution would fit best in Storybook.
Additional context Some discussion of options can be seen here: https://github.com/vitest-dev/vitest/discussions/700#discussioncomment-2251223
Issue Analytics
- State:
- Created 2 years ago
- Reactions:21
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That would make a lot of sense. So it would be something like:
@storybook/addon-storyshots: Core APIs for getting stories/loaders from Storybook. And then:@storybook/addon-storyshots-jest,@storybook/addon-storyshots-vite,@storybook/addon-storyshots-puppeteer,@storybook/addon-storyshots-cypresswhich are all adapters for their respective test-runners.Thoughts @shilman ?
@djindjicdev22 sure, here is our exact code source in our repo: https://github.com/MTES-MCT/camino/blob/master/packages/ui/src/storybook.spec.ts
let me know if you need more information 😃