test-runner icon indicating copy to clipboard operation
test-runner copied to clipboard

🚕 Turn stories into executable tests

Results 136 test-runner issues
Sort by recently updated
recently updated
newest added

### Describe the bug ```session $ npx run test-storybook ● Test suite failed to run Cannot find module '@babel/preset-typescript' Require stack: - /project/node_modules/@babel/core/lib/config/files/plugins.js - /project/node_modules/@babel/core/lib/config/files/index.js - /project/node_modules/@babel/core/lib/index.js - /project/node_modules/@storybook/test-runner/playwright/transform.js -...

bug
dependencies

Added code example in Readme of Global utility functions. The reason is that when a11y rule is configured on story level, the rules are applied in the local Storybook instance...

Jest v29 was recently released ([blog post](https://jestjs.io/blog/2022/08/25/jest-29), [migration guide](https://jestjs.io/docs/upgrading-to-jest29), [changelog](https://github.com/facebook/jest/blob/main/CHANGELOG.md#2900)). The test runner should have support for it. According to the blog post, it should be a straight-forward upgrade.

bug

### Describe the bug Yarn shows a warning when adding `@storybook/test-runner` ### Steps to reproduce the behavior 1. Add `@storybook/test-runner` to a repo ### Expected behavior No missing peer dependency...

bug

### Describe the bug A clear and concise description of what the bug is. ### Steps to reproduce the behavior 1. Create a monorepo that contains stories in multiple packages,...

bug
linear

I seem to get this error seemingly at random when running the tests. Following the stack trace just takes me to the very bottom of my story file. ``` FAIL...

bug

### Describe the bug The test runner runs tests full screen inside the default playwright Chrome viewport. It does not resize the viewport according to the `viewport` parameter of the...

enhancement

### Describe the bug Failed `expect` assertions within `waitFor` cause the test to be marked as failed even if subsequent assertions are successful. `waitFor` is used as per the [documentation](https://testing-library.com/docs/dom-testing-library/api-async/#waitfor)...

bug

`--ci` would be useful to use in CI environments so that the test fails if new snapshots are introduced that have not been committed yet. https://jestjs.io/docs/cli#--ci