-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Storyshot should run tests in parallel #3802
Comments
AFAIR, the most problematic place that takes time is not a tests run, but the storybook initialization. Profiling will help to understand though |
Are you aware of an easy way to profile @igor-dv ? |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook! |
@testerez did you ever manage to get the tests to run in parallel? |
No @patthiel I didn't try. |
I noticed that our storyshots test suite is taking about 13s. Making it by far the slowest test of our project.
From my understanding, jest runs all storyshots tests in a single process because it's declared in a single file. I'm not sure what would be the best way to achieve it but taking advantage of Jest parallelism would probably make things a lot faster.
The text was updated successfully, but these errors were encountered: