Is your feature request related to a problem? Please describe.
When using chromium, if the browser does not start in time, it can cause the test runner to timeout. In these rare cases we'd ideally like to retry the test (and potentially up the timeout limit).
Describe the solution you'd like
Jest provides this functionality through a config option call retryTimes with the following API:
jest.retryTimes(numRetries, options?)
This option should exist in the storybook base config/CLI options.
The output of all the failed attempts should be condensed in the failure report.
Describe alternatives you've considered
There's a couple unideal options:
You would have to run the whole suite again on fail.
You would grep/fetch which tests failed and run those individually again
Both of these present significant challenges in terms of time and effort.
Are you able to assist to bring the feature to reality?
Is your feature request related to a problem? Please describe.
When using chromium, if the browser does not start in time, it can cause the test runner to timeout. In these rare cases we'd ideally like to retry the test (and potentially up the timeout limit).
Describe the solution you'd like
Jest provides this functionality through a config option call
retryTimeswith the following API:This option should exist in the storybook base config/CLI options.
The output of all the failed attempts should be condensed in the failure report.
Describe alternatives you've considered
There's a couple unideal options:
Both of these present significant challenges in terms of time and effort.
Are you able to assist to bring the feature to reality?
no
Additional context
No response