add --testTimeout cli option from jest

README.md

@@ -156,6 +156,7 @@ Usage: test-storybook [options]
 | `--url` | Define the URL to run tests in. Useful for custom Storybook URLs <br/>`test-storybook --url http://the-storybook-url-here.com` |
 | `--browsers` | Define browsers to run tests in. One or multiple of: chromium, firefox, webkit <br/>`test-storybook --browsers firefox chromium` |
 | `--maxWorkers [amount]` | Specifies the maximum number of workers the worker-pool will spawn for running tests <br/>`test-storybook --maxWorkers=2` |
+| `--testTimeout [number]` | This option sets the default timeouts of test cases <br/>`test-storybook --testTimeout=15_000` |
 | `--no-cache` | Disable the cache <br/>`test-storybook --no-cache` |
 | `--clearCache` | Deletes the Jest cache directory and then exits without running tests <br/>`test-storybook --clearCache` |
 | `--verbose` | Display individual test results with the test suite hierarchy <br/>`test-storybook --verbose` |
@@ -173,7 +174,7 @@ Usage: test-storybook [options]
 
 ## Ejecting configuration
 
-The test runner is based on [Jest](https://jestjs.io/) and will accept most of the [CLI options](https://jestjs.io/docs/cli) that Jest does, like `--watch`, `--watchAll`, `--maxWorkers`, etc. It works out of the box, but if you want better control over its configuration, you can eject its configuration by running `test-storybook --eject` to create a local `test-runner-jest.config.js` file in the root folder of your project. This file will be used by the test runner.
+The test runner is based on [Jest](https://jestjs.io/) and will accept most of the [CLI options](https://jestjs.io/docs/cli) that Jest does, like `--watch`, `--watchAll`, `--maxWorkers`, `--testTimeout`, etc. It works out of the box, but if you want better control over its configuration, you can eject its configuration by running `test-storybook --eject` to create a local `test-runner-jest.config.js` file in the root folder of your project. This file will be used by the test runner.
 
 > **Note**
 > The `test-runner-jest.config.js` file can be placed inside of your Storybook config dir as well. If you pass the `--config-dir` option, the test-runner will look for the config file there as well.
@@ -1018,6 +1019,12 @@ In either way, to fix it you should limit the amount of workers that run in para
 }
 ```
 
+Another option is trying to increase the test timeout by passing the [--testTimeout](https://jestjs.io/docs/cli#--testtimeoutnumber) option to your command (adding `--testTimeout=60_000` will increase test timeouts to 1 minute):
+
+```json
+"test-storybook:ci": "concurrently -k -s first -n \"SB,TEST\" -c \"magenta,blue\" \"yarn build-storybook --quiet && npx http-server storybook-static --port 6006 --silent\" \"wait-on tcp:6006 && yarn test-storybook --maxWorkers=2 --testTimeout=60_000\""
+```
+
 #### The test runner reports "No tests found" running on a Windows CI
 
 There is currently a [bug](https://github.com/facebook/jest/issues/8536) in Jest which means tests cannot be on a separate drive than the project. To work around this you will need to set the `TEMP` environment variable to a temporary folder on the same drive as your project. Here's what that would look like on GitHub Actions:

src/util/getParsedCliOptions.ts

@@ -39,6 +39,7 @@ export const getParsedCliOptions = (): ParsedCliOptions => {
  '--maxWorkers <amount>',
  'Specifies the maximum number of workers the worker-pool will spawn for running tests'
  )
+ .option('--testTimeout <number>', 'This option sets the default timeouts of test cases')
  .option('--no-cache', 'Disable the cache')
  .option('--clearCache', 'Deletes the Jest cache directory and then exits without running tests')
  .option('--verbose', 'Display individual test results with the test suite hierarchy')