Latest valid Sauce Labs browser, simulator and emulator versions are listed as not available
cgonzalescdm opened this issue · comments
Latest Sauce Labs browser, simulator, and emulator versions are listed as not available even though they are available in the Sauce Labs platform configurator - https://saucelabs.com/platform/platform-configurator#/.
Instead of using the deprecated wiki assets page (example: https://wiki-assets.saucelabs.com/data/selenium_pc_windows-10.json), the Sauce Labs platform API (https://docs.saucelabs.com/dev/api/platform/) should be used when verifying the version is valid.
Could you please clarify where you see that the current assets page is deprecated?
if it is really so, we would accept the PR request with required changes.
Sorry for the super late response.
To find out about the wiki page no longer being updated, I opened a saucelabs support ticket about the wiki page and the response was:
"The wiki-assets json objects are very much out of date, as you mentioned and can't be relied upon.
If you'd like to continue to use testcafe-browser-provider-saucelabs effectively, you'd need to point the team to our Platform API: https://docs.saucelabs.com/dev/api/platform/"
In the example wiki-assets URL, the latest specific chrome version (not 'latest' as the value) is 91.0. So if a user attempts to specify a version later than that, an error occurs:
Error: Cannot find the browser. "saucelabs:Chrome@92.0:Windows 10" is neither a known browser alias, nor a path to an executable file.
Bypassing the check or updating how it verifies a valid version seems to be needed.
Thank you for sharing this information. We have already planned our tasks for the near future. However, since wiki-assets is outdated, we would accept the PR if you make it.
@AlexKamaev do you folks have a bug bounty program for feature requests or bug fixes? If there is another channel for this type of requests, please let me know.
Hi @diemol,
We don't have a bounty program. Let me know if you have further questions.
👋 @AlexKamaev, we were only wondering if there are ways to support or pay for specific features like this one, sometimes we do not have the context or knowledge to make changes ourselves.
@diemol, We don't create features or fixes for payment, and we don't pay contributors either. We just accept and review PRs. @alexplischke has already created PR with migration. You can contact him and thank him in the way you want.
@Aleksey28 thank you. @alexplischke's team did not have time, but seems they reorganized priorities, nice!
Hello everyone involved! Will there be a chance to get to know when #81 is going to be reviewed and merged -> published?
Thank you very much in advance!
Hi @apolonskiy,
I reviewed PR #81 and requested some changes.
I was wondering if you could help me with figuring out, when should we expect 2.0.0 published in npm, since MR is merged now? Thanks in advance @miherlosev!
Hi @apolonskiy,
The testcafe-browser-provider-saucelabs@2.0.0 module is released.