We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--watch
When running npx test-storybook --watch the test runner runs in normal mode, rather than watching for changes and exists on completion
npx test-storybook --watch
Bug encountered in a private repo, is there a good starter project I can test deps on?
I'd expect --watch to watch for file changes and rerun test-storybook accordingly
If applicable, add screenshots and/or logs to help explain your problem.
"@storybook/test-runner": "^0.6.0-next.1", "@storybook/testing-library": "^0.0.13", "@storybook/testing-react": "^1.3.0", "jest": "^28.1.3",
Add any other context about the problem here.
associated discord thread: https://discord.com/channels/486522875931656193/1006156600022667345/1006157098318577714
I think I may have discovered it being due to upgrading to jest 28 in our repo?
The text was updated successfully, but these errors were encountered:
yay https://github.com/storybookjs/test-runner/releases/tag/v0.6.0-next.3
Sorry, something went wrong.
Fix was released in v0.6.0! Thanks once again @jasikpark
No branches or pull requests
Describe the bug
When running
npx test-storybook --watch
the test runner runs in normal mode, rather than watching for changes and exists on completionSteps to reproduce the behavior
Bug encountered in a private repo, is there a good starter project I can test deps on?
Expected behavior
I'd expect
--watch
to watch for file changes and rerun test-storybook accordinglyScreenshots and/or logs
If applicable, add screenshots and/or logs to help explain your problem.
Environment
Additional context
Add any other context about the problem here.
associated discord thread: https://discord.com/channels/486522875931656193/1006156600022667345/1006157098318577714
I think I may have discovered it being due to upgrading to jest 28 in our repo?
The text was updated successfully, but these errors were encountered: