-
Notifications
You must be signed in to change notification settings - Fork 28
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
Feature Request: Latest and Previous versions for BrowserStack #20
Comments
I am going to be helping out on this. Documenting my requirements here for completeness, though it goes beyond the scope of the original request. Version math. This means being able to say Version ranges. For example, Internet Explorer I'm not sure whether using different syntax for each vs just treating An easy way of dealing with some of this would be to embrace actual semver, which many Intern users will already be familiar with. The browsers don't even have to be compliant for this to work well. However, I don't believe it has a way to say |
Also consider SauceLabs Selenium version spec. They support Note that we can already do version ranges in a sense by specifying multiple versions in an array for If by semver you mean npm's version ranges, I could see that being potentially useful. Is it common for people to want to test ranges of more than a couple browser versions, or more than a couple that aren't contiguous with 'latest'? |
By 'consider SauceLabs' I just mean that they have a syntax for this now, so it may be good to follow, particularly since it would basically be a pass-through for the SauceLabsTunnel. |
Yeah, BrowserStack has something similar. Would be nice to see a standard across providers, but I'm not holding my breath. :)
This works well for some things. But it breaks down when it comes time to say Safari
This is probably more of a power user case, but yeah that's happened to me on enterprise applications now and then. We need to support a slew of installations, but some new browser comes out that breaks things and it takes us a while to respond with a real fix. In the meantime, we can't support anything past a certain version. |
Howdy, I have a work in progress supporting 'previous' and 'latest' version aliases on my digdug fork. It should be pretty straight forward to extend it to use latest-x nomenclature. Please have a look. Tunnel: https://github.com/devpaul/digdug/blob/version_alias/Tunnel.js#L559-L573 SauceLabsTunnel: https://github.com/devpaul/digdug/blob/version_alias/SauceLabsTunnel.js#L461-L472 BrowserStackTunnel: https://github.com/devpaul/digdug/blob/version_alias/BrowserStackTunnel.js#L270-L323 |
Browserstack's only works with their JS provider, which uses some BS-specific APIs to get information about available browsers. Sauce's works through the standard Selenium capabilities interface, which is much more convenient (for us). However, Sauce's implementation won't work for ranges, so in that respect it really doesn't buy us much.
Makes sense. So maybe we just need 2 syntaxes, at least for now, something like 'latest - x' and 'version1 .. version2' (e.g., '6 .. latest - 1')? |
I'm updating the code to support a more complex set of ranges, aliases, and math. Supported version types and ranges:
|
Sweet. :) Personally, I don't think |
Since we are already supporting environments: [
{ browserName: 'firefox', version: 'latest' },
{ browserName: 'firefox', version: 'previous' },
] If somebody wants to use |
Fair enough. Just my Python background peeking through. :) |
Hmmm...I agree with @sholladay regarding 'previous'. In general, Intern prefers to have only one way to do things. |
This has been added in commits 96aa488 and theintern/intern@ab9a245. Thanks @devpaul! It will be included in the next releases of Dig Dug and Intern. |
It would be good if one can specify
latest
andprevious
version for Browserstack tunnel to reference the current and previous versions for the browsers available on browserstack. This feature is available in browserstack-runner as of now: https://github.com/browserstack/browserstack-runner#compact-browsers-configurationThe text was updated successfully, but these errors were encountered: