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
Is there any ability to set the format of the screenshot filenames created by nightwatch? The documentation currently only shows the ability to configure the following: enabled, path, on_failure, on_error.
It would be nice to be able to have another one for 'filenameformat' or something similar. Currently it creates files with the following:
Our Jenkins build creates a download link to these files along with the other build artifacts after a failed build and the current format is causing 404 errors trying to retrieve them, meaning we actually have to RDP onto the build server to retrieve them.
Also not sure what is causing the last ) to not be there.
This issue has been automatically marked as stale because it has not had any recent activity.
If possible, please retry using the latest Nightwatch version and update the issue with any relevant details. If no further activity occurs, it will be closed. Thank you for your contribution.
Is there any ability to set the format of the screenshot filenames created by nightwatch? The documentation currently only shows the ability to configure the following: enabled, path, on_failure, on_error.
It would be nice to be able to have another one for 'filenameformat' or something similar. Currently it creates files with the following:
<test_name>_FAILED_Oct-26-2017-095542-GMT+0000-(Coordinated-Universal.png
Our Jenkins build creates a download link to these files along with the other build artifacts after a failed build and the current format is causing 404 errors trying to retrieve them, meaning we actually have to RDP onto the build server to retrieve them.
Also not sure what is causing the last ) to not be there.
Documentation link used: https://github.com/nightwatchjs/nightwatch-docs/blob/master/gettingstarted/configuration/config-test-settings.md
Thanks.
The text was updated successfully, but these errors were encountered: