Selecting platforms requiring WebDriver 3 capabilities doesn't work

[DylanLacey]

The plugin currently doesn't properly support WebDriver 3 capabilities.

For example, in a job configured with Google Nexus 7 HD in Landscape, the environment variables were set as SAUCE_ONDEMAND_BROWSERS=[{"os":"android","browser":"android","browser-version":"4.3","platform":"ANDROID","url":"sauce-ondemand:?os=android&browser=android&browser-version=4.3"}].

The specific device was not requested, and the rotation was missing.

[andr-t]

It would be great if it outputted values consistent with the Platform Configurator, including Appium capabilities.

Bamboo Sauce 1.6.67:

{ os: 'Mac 10.9',
browser: 'chrome',
'browser-version': '48',
platform: 'MAC',

PC:

caps = {browserName: 'chrome'};
caps['platform'] = 'OS X 10.9';
caps['version'] = '48.0';

[halkeye]

Hey @andr-t, this is something I really want to. I've been trying to get better apis so the data can be consistent.

For the bamboo sauce stuff, how do you get the data into your project? Env variables? Which envs do you use?

[andr-t]

Hi @halkeye, we use access keys, host+port, and build number, plus our own vars set in Bamboo (URLs, client IDs). We then read these vars and build capabilities to pass to our test runner.

The most helpful feature for us would be the ability to easily configure platforms, perhaps even showing most recent ones on top or building profiles users can select from. Global options like toggling screenshots and video are also useful.

[halkeye]

@andr-t so you don't use any of the ENVs for the (broken) platform pickers? I'm confused where the first example is coming from then.

[andr-t]

Sorry I thought you meant additional envs. For the platform picker we use 'bamboo_SAUCE_ONDEMAND_BROWSERS', which holds values from the multi-select as a JSON array.