generated from storybookjs/addon-kit
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
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
[Bug] Sync issue in failures from one test affecting another test #62
Comments
Removing the following code from the testPrefixer in page.on('pageerror', (err) => {
page.evaluate(({ id, err }) => __throwError(id, err), { id: %%id%%, err: err.message });
}); It isn’t an ideal solution. Maybe I can find the cause in the |
Closed
I recently updated the pr #264 to change the proposed fix for this issue. |
🚀 Issue was released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This seems not to be an actual bug in the test-runner, but rather in Storybook. Here's an example of a diagram that shows the sequence of steps in the test-runner:
Steps to reproduce the behavior
Demo
story inButton.stories.js
from:to:
The
boom
error should not leak into theFindBy
story, which actually does not even use the same component asDemo
:The text was updated successfully, but these errors were encountered: