Skip to content
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

Handle 'test error' to deal with error response from invalid browsers. #225

Closed

Conversation

jbeard4
Copy link

@jbeard4 jbeard4 commented Apr 5, 2017

Tested with configuration:

      'saucelabs-custom': {
        all: {
          options: {
            urls: [
              'http://127.0.0.1:3000/'
            ],
            browsers: [
              {
                browserName : 'chrome',
                platform : 'OS X 10.11',
                version : 26 
              }
            ],
            statusCheckAttempts : -1
          }
        }
      }

Chrome 26 on OS X 10.11 is unsupported by sauce labs. Returns a response where result.status is "test error". Expected behavior: test fails with an error. Actual behavior: request will be re-attempted, and when statusCheckAttempts is set to -1, the test will never complete.

This PR causes the test to complete with an error.

@jbeard4
Copy link
Author

jbeard4 commented Apr 5, 2017

I just noticed, this is a duplicate of #224

@jbeard4 jbeard4 closed this Apr 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant