We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.44.0
playwright test --ui --output=some/other/path
playwright test --output=some/other/path
I'd expect the --output option to be respected as it was before 1.43.0
--output
The --output option is ignored when running with --ui
--ui
This also affects testInfo.outputPath() from within a test fixture but I assume this is all due to the same root issue.
testInfo.outputPath()
System: OS: Windows 10 10.0.19045 CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor Memory: 7.55 GB / 15.95 GB Binaries: Node: 20.13.1 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD npm: 10.5.2 - C:\Program Files\nodejs\npm.CMD IDEs: VSCode: 1.89.1 - C:\Users\User\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD Languages: Bash: 4.4.23 - C:\Program Files\Git\usr\bin\bash.EXE npmPackages: @playwright/test: ^1.44.0 => 1.44.0
The text was updated successfully, but these errors were encountered:
chore: pass outputDir to uimode (#30941)
7b27fc3
Fixes #30886
Thank you so much for the fast turnaround on this fix! Is there an ETA for 1.45.0 being released?
Sorry, something went wrong.
pavelfeldman
Successfully merging a pull request may close this issue.
Version
1.44.0
Steps to reproduce
playwright test --ui --output=some/other/path
a. When you close the UI, the output will not be generated at the specified path
playwright test --output=some/other/path
a. When the tests end, the output will be at the specified path
Expected behavior
I'd expect the
--output
option to be respected as it was before 1.43.0Actual behavior
The
--output
option is ignored when running with--ui
Additional context
This also affects
testInfo.outputPath()
from within a test fixture but I assume this is all due to the same root issue.Environment
The text was updated successfully, but these errors were encountered: