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
I've hit a situation where tests are passing in the browser, but not in the test-runner. Without having some way to inspect the state of my story in the test-runner, it's very difficult to troubleshoot what is happening. I propose one of two things:
Send all console output to the terminal in the case of failing tests. There could be useful information which can help debug the reason for the failure, so it should be provided to the user. Passing tests should not output console warnings or logs.
Add a flag to send all console output to the terminal, for passing and failing tests. I think this is less desirable, because it's another flag that people have to learn.
The text was updated successfully, but these errors were encountered:
I tried poking around to find a way to make this happen, without luck so far. But as a workaround, I can add a .storybook/test-runner.cjs with the contents:
Describe the feature
I've hit a situation where tests are passing in the browser, but not in the test-runner. Without having some way to inspect the state of my story in the test-runner, it's very difficult to troubleshoot what is happening. I propose one of two things:
Send all console output to the terminal in the case of failing tests. There could be useful information which can help debug the reason for the failure, so it should be provided to the user. Passing tests should not output console warnings or logs.
Add a flag to send all console output to the terminal, for passing and failing tests. I think this is less desirable, because it's another flag that people have to learn.
The text was updated successfully, but these errors were encountered: