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
I am having an issue running through jenkins (linux) against a windows selenium grid node chrome download path gets converted to a path with forward slashes. I have tried using both the properties file and the conf file and get the same result.
the S drive is mounted to a samba network share. If I look in the console window for the node I see the following capability:
I checked the download folder path in the chrome browser running on the Windows selenium grid (even tried latest 4 release) and the download path is set to S:/Export. Chrome on windows does not even allow you to enter this manually.
I was able to work around the issue by using the Serenity BeforeAWebdriverScenario extension and changing the path back to S:\Export after which the test executed fine.
This is occurring on even the Serenity 3.2.1 release.
The text was updated successfully, but these errors were encountered:
I am having an issue running through jenkins (linux) against a windows selenium grid node chrome download path gets converted to a path with forward slashes. I have tried using both the properties file and the conf file and get the same result.
conf file:
chrome_preferences {
download {
default_directory="S:\\export"
}
}
Or
serenity.properties:
chrome_preferences.download.default_directory=S:\export
the S drive is mounted to a samba network share. If I look in the console window for the node I see the following capability:
I checked the download folder path in the chrome browser running on the Windows selenium grid (even tried latest 4 release) and the download path is set to S:/Export. Chrome on windows does not even allow you to enter this manually.
I was able to work around the issue by using the Serenity BeforeAWebdriverScenario extension and changing the path back to S:\Export after which the test executed fine.
This is occurring on even the Serenity 3.2.1 release.
The text was updated successfully, but these errors were encountered: