Support specifying "latest" as a browser versions of Chrome
richardxia opened this issue · comments
According to the SauceLabs documentation, you can specify "latest", "latest-1", "latest-2", etc. to get the latest stable releases of Chrome or Firefox. For example, if Chrome 73 is the latest stable release, "latest" will point to 73, "latest-1" will point to 72, etc.
When I try specifying a "latest" version in TestCafe, I get the following error message:
ERROR Unable to find the browser. "saucelabs:Chrome@latest-1:Windows 10" is not a browser alias or path to an executable file.
Since my project is open source, I can point you to the exact commit and the Travis CI build which contains this error message:
- ShelterTechSF/askdarcel-web@f4fd392
- https://travis-ci.org/ShelterTechSF/askdarcel-web/builds/514785137?utm_source=github_status&utm_medium=notification
Is this the correct library for making this change? It's hard for me to tell exactly which library is responsible for the error.
The latest and latest-N version specifiers are not supported by this browser provider yet. It will be nice if you implement this feature. I guess you can start with the _filterPlatformInfo function and modify it to support latest and latest-N. Take a look at how this function handles the any version specifier: https://github.com/DevExpress/testcafe-browser-provider-saucelabs/blob/master/src/index.js#L273
Just wanted to comment that I think this has been fixed. I've specified my browser as saucelabs:Chrome@latest:Windows 10 and am running testcafe via TravisCI. I can see on the SauceLabs end that my tests are getting run on the latest Chrome version (91).