Support Storybook test-runner
See original GitHub issue- I’d be willing to implement this feature (contributing guide)
Description
I’d like to see support for Storybook Test Runner.
Motivation
it’s becoming the de-facto way of testing components (compared to creating a separated cypress config).
Suggested Implementation
Not sure how to help/where to start. I guess a test-storybook
executor ?
Alternate Implementations
One could forge a workaround using the run-commands
executors, but it won’t scale well 😃.
Thanks for the awesome work team!
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Test runner Addon | Storybook: Frontend workshop for UI ...
The Storybook test runner uses Jest as a runner, and Playwright as a testing framework. Each one of your .stories files is transformed...
Read more >@storybook/test-runner - npm
Test runner for Storybook stories. Latest version: 0.9.2, last published: 5 days ago. Start using @storybook/test-runner in your project by ...
Read more >Issues · storybookjs/test-runner - GitHub
Turn stories into executable tests. Contribute to storybookjs/test-runner development by creating an account on GitHub.
Read more >Code coverage with Storybook test runner - Medium
How do you ensure your tests cover all of them? Coverage reports let you see the percentage of code is executed by tests...
Read more >npm:@storybook/test-runner - Skypack.dev
By default, the test runner transforms your story files into tests. It also supports a secondary "stories.json mode" which runs directly ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Djiit The best way to do it is to follow the steps described here. Build
nx
and then publish it with verdaccio to a local registry.The other way to do it (more sloppy I guess), is to create a Nx workspace normally, and then go in node_modules and make the changes you made to the code.
Just gave a first stab at it. Added a test. How can I easly test it locally within a project ?