-
Notifications
You must be signed in to change notification settings - Fork 65
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
[bug] the --outputFile parameter is not working when --junit parameter is issued #443
Comments
Hey @squidjam thanks for reporting this! I don't think it's an actual issue 🤔 1 - the |
Hello, thank you for your answer. |
Thanks for explaining! Would you mind sharing a minimal reproduction so I can take a look at? |
Thanks, after further reading, the way described by you should be the right way to do it. Cheers. For future reference: I just thought it would be easier to pass through the parameter --output and have test-runner reroute it as the JEST_JUNIT_OUTPUT_NAME="name.xml" when it invokes junit itself. |
Describe the bug
When you issue the --junit parameter to generate a junitXML test report, the --outputFile parameter doesn't allow you to set the name of the output report file (but it does on --json), and a file with a default name (junit.xml) is generated.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The output report file should be named using the --outputFile parameter value
Screenshots
System
Storybook Environment Info:
System:
OS: Windows 11 10.0.22000
CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12800H
Binaries:
Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD <----- active
npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
pnpm: 8.5.1 - ~\AppData\Roaming\nvm\v18.12.1\pnpm.CMD
Browsers:
Edge: Spartan (44.22000.2600.0), Chromium (122.0.2365.92)
npmPackages:
@storybook/addon-a11y: ^8.0.0 => 8.0.0
@storybook/addon-designs: ^7.0.9 => 7.0.9
@storybook/addon-essentials: ^8.0.0 => 8.0.0
@storybook/addon-interactions: ^8.0.0 => 8.0.0
@storybook/addon-links: ^8.0.0 => 8.0.0
@storybook/addon-mdx-gfm: 8.0.0 => 8.0.0
@storybook/blocks: ^8.0.0 => 8.0.0
@storybook/react: ^8.0.0 => 8.0.0
@storybook/react-vite: ^8.0.0 => 8.0.0
@storybook/test: 8.0.0 => 8.0.0
@storybook/test-runner: ^0.17.0 => 0.17.0
eslint-plugin-storybook: ^0.8.0 => 0.8.0
storybook: ^8.0.0 => 8.0.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: