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
Describe the bug --failOnConsole test parameter is not working (if a test finishes too fast)
To Reproduce
Steps to reproduce the behavior:
clone this repo git clone https://github.com/ts213/storybook-test-bug
install deps npm i
launch storybook server npm run storybook
open a browser console on a newly opened page and verify that the console contains the error: [MSW] Error: captured a request without a matching request handler....
now run the test-storybook command: npm run test-storybook -- --failOnConsole
test successfully passes: Test Suites: 1 passed, 1 total
Expected behavior
Test should fail.
System
Please paste the results of npx storybook@latest info here.
Additional context
I can make test fail if I deliberately delay a test:
uncomment this line await new Promise((resolve, reject) => setTimeout(resolve, 1100));
in src/stories/Page.stories.js
The text was updated successfully, but these errors were encountered:
Describe the bug
--failOnConsole
test parameter is not working (if a test finishes too fast)To Reproduce
Steps to reproduce the behavior:
clone this repo
git clone https://github.com/ts213/storybook-test-bug
install deps
npm i
launch storybook server
npm run storybook
open a browser console on a newly opened page and verify that the console contains the error:
[MSW] Error: captured a request without a matching request handler....
now run the test-storybook command:
npm run test-storybook -- --failOnConsole
test successfully passes:
Test Suites: 1 passed, 1 total
Expected behavior
Test should fail.
System
Please paste the results of
npx storybook@latest info
here.Additional context
I can make test fail if I deliberately delay a test:
uncomment this line
await new Promise((resolve, reject) => setTimeout(resolve, 1100));
in
src/stories/Page.stories.js
The text was updated successfully, but these errors were encountered: