-
Notifications
You must be signed in to change notification settings - Fork 672
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
Make path pattern smarter for errors screenshots #7014
Comments
Hi @fmancardi, This behavior is expected. TestCafe replaces any |
I'm going to provide a more detailed explanation, because IMHO replace is not working as expected for errors |
Fine, please share more details, but before you do that, take a look at this paragraph. In the example with the default path pattern, you can see that the |
Please give a look to my first explanation, the errors folder does not exist anymore, it's name is changed to TC-004-errors. regards |
Thank you for the explanation. It happens because you separate |
I've tried with same effect |
It doesn't change anything. In case of errors, testcafe replaces part of the |
Using your suggestions things work as expected. May be a more flexible approach can be to have two pathPatters:
Best regards |
Thank you for the suggestion. We will consider ways to improve this behavior and update this thread once we have news. |
Release v3.5.0-rc.1 addresses this. |
1 similar comment
Release v3.5.0-rc.1 addresses this. |
What is your Scenario?
I would like that screenshots on failure generate a file name with the testcase name + a progressive.
Probably this a non-sense because when test script fails it can not take more than one screenshot.
This is my .testcaferc.json
What is the Current behavior?
for the screenshots taken usin .takeScreenshot() it work as expected generating
inside the TCF-004-errors folder, file name is the standard
What is the Expected behavior?
inside the TCF-004-errors folder, file name respect the mask
${TEST}-${FILE_INDEX}.png
What is your public website URL? (or attach your complete example)
You can access our test site
This is the example
What is your TestCafe test code?
Your complete configuration file
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
N.A.
TestCafe version
1.18.2
Node.js version
v14.15.5
Command-line arguments
testcafe 'chrome --start-fullscreen' --test-meta WKFSTATUS=ready,6.4=yes --cfg=at-7.0.json ./test/testcafe/TCF-006-multiple-sshots.js
Browser name(s) and version(s)
No response
Platform(s) and version(s)
Windows 10, using Gitbash to run the script
Other
No response
The text was updated successfully, but these errors were encountered: