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
Node.js version: v14.16.1 Windows version: 10 WebStorm version 2021.1.3
What happened? / Describe the bug
I record a trace for each test that I perform.
In order to avoid file overwriting - I use the title of the test (testInfo.title) as the name of the file (see the complete code in the section below).
After test performing - I get the following trace zipped folder:
As can be seen - the name of the zipped folder is 'Search and buy item.zip'.
In order to open the trace of the test, I use the "npx playwright show-trace" command via the IDE terminal. Using the terminal autocompletion - I get the following path:
But the attempt to perform this command with the provided path - triggers error:
Only if I'll remove the spaces from the zipped directory (for example: 'Searchandbuyitem.zip') - it will work as well.
Playwright version
1.12.3
Operating system
Windows
What browsers are you seeing the problem on?
No response
Other information
Node.js version: v14.16.1
Windows version: 10
WebStorm version 2021.1.3
What happened? / Describe the bug
I record a trace for each test that I perform.
In order to avoid file overwriting - I use the title of the test (testInfo.title) as the name of the file (see the complete code in the section below).
After test performing - I get the following trace zipped folder:
As can be seen - the name of the zipped folder is 'Search and buy item.zip'.
In order to open the trace of the test, I use the "npx playwright show-trace" command via the IDE terminal. Using the terminal autocompletion - I get the following path:
But the attempt to perform this command with the provided path - triggers error:
Only if I'll remove the spaces from the zipped directory (for example: 'Searchandbuyitem.zip') - it will work as well.
See the full code in the section below.
Code snippet to reproduce your bug
Relevant log output
No response
The text was updated successfully, but these errors were encountered: