2) The second error I'm running into is that the webdriver command is defaulting to the Linux OS when running tests in SauceLabs when using the Chrome and Firefox browsers (IE is determined to be under Windows). This bug occurs when passing in either "Windows 7" or "Windows 2008" as the OS capability using the "–cap platform=Windows 7" option for the webdriver wrapper script.
The specific error that is presented is below:
[WARN] Requested resolution 1280×1024 is not supported for this OS/browser/version/device combo. Retrying w/o requesting any specific resolution.
Launching test suite, OS: Linux, browser: Chrome 48.0.2564.97
I've confirmed that SauceLabs supports this resolution for Windows 7 / Chrome and Windows 7 / Firefox.
I hope this helps and that we can see a bugfix for these issues. Please let me know if you have any other questions.
The browser variable is quoted there. Perhaps there is something in the additional options that is causing the issue? Would the output from debug mode be helpful to you?
It's been a while but I was finally able to come back to this issue.
Here's a boiled down reproducible test case:
# Does NOT use the correct browser
$ SELENIUM_BROWSER=chrome SELENIUM_PLATFORM="Windows 7" SELENIUM_VERSION=52 \
./src/vendor/siesta/bin/webdriver "redacted" \
--cap browserName="${SELENIUM_BROWSER}" \
--cap platform="${SELENIUM_PLATFORM}" \
--cap version="${SELENIUM_VERSION}" \
--saucelabs="redacted"
Launching local tunnel to SauceLabs: automation_jenkins
[WARN] Requested resolution 1280x1024 is not supported for this OS/browser/version/device combo. Retrying w/o requesting any specific resolution.
Launching test suite, OS: Linux, browser: Chrome 48.0.2564.97
...
# Works as expected
$ ./src/vendor/siesta/bin/webdriver "https://redacted" \
--cap browserName="chrome" \
--cap platform="Windows 7" \
--cap version="52" \
--saucelabs="redacted"
Launching local tunnel to SauceLabs: automation_jenkins
Launching test suite, OS: Windows, browser: Chrome 52.0.2743.82
...
It seems that having the SELENIUM environmental variables causes the wrong browser to be set. These variables are automatically set by the Jenkins Sauce OnDemand Plugin so I can't just rename them. I'm able to reproduce this outside of Jenkins in my dev environment. I'm using Siesta v4.2.2.