You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test against firefox_45, safari_9, safari_10, safari_11.
Actual Behavior
/browserstack-runner/bin/cli.js:401
if (browser.browser_version === 'latest') {
^
TypeError: Cannot read property 'browser_version' of undefined
at /qunit/node_modules/browserstack-runner/bin/cli.js
at Array.forEach (<anonymous>)
at /qunit/node_modules/browserstack-runner/bin/cli.js
at Timeout._onTimeout (/qunit/node_modules/browserstack-runner/lib/local.js)
browserstack.json
"browsers": [
"safari_9"
],
Platform details
browserstack-runner version: 0.9.4
node version: 10.x
The text was updated successfully, but these errors were encountered:
When no match is found, the process would just crash. Instead, recognise
this as a normal end-user scenario and point them to the list of
available workers.
In my experience the most common way to encounter this issue is when
additional decimal places are required by the API, e.g. "safari"
"9" results in a crash, because the available workers are described
as "9.1" instead. Given that most browers are described without a
decimal place, this is an easy mistake to make.
Another way to get this is when there is a misspelled browser name.
Before:
```
TypeError: Cannot read property 'browser_version' of undefined
at browserstack-runner/bin/cli.js
```
After:
```
Error: No desktop match found for {"browser":"safari","browser_version":"9"}
Check https://www.browserstack.com/list-of-browsers-and-platforms/js_testing
at populateOsAndOsVersion (browserstack-runner/lib/configParser.js)
```
Fixesbrowserstack#243.
Expected Behavior
Test against
firefox_45
,safari_9
,safari_10
,safari_11
.Actual Behavior
browserstack.json
Platform details
0.9.4
The text was updated successfully, but these errors were encountered: