-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot pin tunnel browser to SemVer version #1178
Comments
The validator could be updated to accept version strings (x.y.z.w) rather than only simple numbers. |
|
The validation could be relaxed. The core issue is just that local selenium grids weren't considered when the resolution code was written. Cloud services were the prime driver of the version resolution code, and they all support abbreviated versions (e.g., Regarding |
SauceLabs support a |
Yeah, that's where Intern's 'latest' alias support came from. Intern just lets that version style be applied to other cloud services as well. A similar thing could be done with a selenium grid since Selenium provides an endpoint to retrieve all the available browsers supported by the grid. |
Expected behavior
Pin a particular browser version on a remote Selenium grid.
Current behavior
Setting to "87" throws an error on the grid as it is not an exact match.
Possible solution
Remove number validation if it is not necessary for other services.
intern/packages/core/src/lib/resolveEnvironments.ts
Line 169 in a3b9643
Intern: 4.8.4
The text was updated successfully, but these errors were encountered: