Description
Current behavior is to use System installed Chrome by default.
I think a good case can be made for defaulting to using Chrome for Testing, but I can understand if that might not be the expected behavior from users. It would certainly be a breaking change not to make lightly.
At the very least we should make it easier for users to specify they want to use CfT. The only option we have right now requires users to set SE_FORCE_BROWSER_DOWNLOAD (which is a little misleading because it doesn't always download if it exists in cache). To complicate things users would also want to set SE_SKIP_DRIVER_IN_PATH so that they don't end up with system driver and CfT browser (this is what would happen on Github Actions Runner)
I see 2 options not mutually excusive
- We can add SE_USE_DOWNLOADED_BROWSER which will set SE_FORCE_BROWSER_DOWNLOAD and SE_SKIP_DRIVER_IN_PATH
- We create a method in Options classes for this. Either useDownloadedBrowser or even useChromeForTesting in chrome options.
Have you considered any alternatives or workarounds?
No response
Description
Current behavior is to use System installed Chrome by default.
I think a good case can be made for defaulting to using Chrome for Testing, but I can understand if that might not be the expected behavior from users. It would certainly be a breaking change not to make lightly.
At the very least we should make it easier for users to specify they want to use CfT. The only option we have right now requires users to set SE_FORCE_BROWSER_DOWNLOAD (which is a little misleading because it doesn't always download if it exists in cache). To complicate things users would also want to set SE_SKIP_DRIVER_IN_PATH so that they don't end up with system driver and CfT browser (this is what would happen on Github Actions Runner)
I see 2 options not mutually excusive
Have you considered any alternatives or workarounds?
No response