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
If your project is in a folder that has a space in it, Vitest cannot find your tests. This may be a bug with Vitest but since it gives a specific error for Storybook I'll log it here. This could be windows only, unsure.
Create any Storybook project, with the test addon as described here : https://storybook.js.org/docs/writing-tests/test-addon
Ensure that the path is something like c:\my projects\storybook\src with a space somewhere in the path
When I execute npm run test, I get the following error for all stories. Note that I do not have any specific spec/test files, at this stage I'm just using it as a smoke test.
Error: No test suite found in file C:/my projects/storybook/src/stories/global/popover/popover.stories.tsx
If I remove the space in "my projects" the tests all run fine.
I'm not sure if this should be added to the docs because it is "true" that I do not have specific test suite files in those files (They are simply stories), so I thought maybe I had to write specific spec files etc.
Describe the bug
If your project is in a folder that has a space in it, Vitest cannot find your tests. This may be a bug with Vitest but since it gives a specific error for Storybook I'll log it here. This could be windows only, unsure.
Create any Storybook project, with the test addon as described here : https://storybook.js.org/docs/writing-tests/test-addon
Ensure that the path is something like c:\my projects\storybook\src with a space somewhere in the path
When I execute npm run test, I get the following error for all stories. Note that I do not have any specific spec/test files, at this stage I'm just using it as a smoke test.
If I remove the space in "my projects" the tests all run fine.
I'm not sure if this should be added to the docs because it is "true" that I do not have specific test suite files in those files (They are simply stories), so I thought maybe I had to write specific spec files etc.
Reproduction link
http://no.com
Reproduction steps
No response
System
Storybook Environment Info:
System:
OS: Windows 10 10.0.19045
CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-1245U
Binaries:
Node: 20.10.0 - C:\Node\node-v20.10.0-win-x64\node.EXE
npm: 10.2.3 - C:\Node\node-v20.10.0-win-x64\npm.CMD <----- active
Browsers:
Edge: Chromium (128.0.2739.42)
npmPackages:
@storybook/addon-a11y: ^8.4.2 => 8.4.2
@storybook/addon-essentials: ^8.4.2 => 8.4.2
@storybook/addon-links: ^8.4.2 => 8.4.2
@storybook/blocks: ^8.4.2 => 8.4.2
@storybook/experimental-addon-test: ^8.4.2 => 8.4.2
@storybook/react: ^8.4.2 => 8.4.2
@storybook/react-vite: ^8.4.2 => 8.4.2
@storybook/test: ^8.4.2 => 8.4.2
@storybook/test-runner: ^0.19.1 => 0.19.1
eslint-plugin-storybook: ^0.11.0 => 0.11.0
storybook: ^8.4.2 => 8.4.2
Additional context
No response
The text was updated successfully, but these errors were encountered: