Support for "localIdentifier" setting/capability & Avoiding testem default browser start timeout #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As described in https://docs.travis-ci.com/user/browserstack/ and https://www.browserstack.com/automate/travisci, when using Selenium there is a identifier associated with each local connection created, and it is provided in the environment variable BROWSERSTACK_LOCAL_IDENTIFIER and must be included in the settings. The change in this commit takes the ruby selenium webdriver example described in above links, and provides the same steps for this testem browserstack integration.
Testem has a default browser start timeout of 30 seconds, which hits few times while trying to run BrowserStack tests using testem. The default setting is being overridden with a timeout of 600 (10 minutes) which should avoid this in most cases. The error message that pops up when this timeout occurs is the following: "Browser failed to connect within 30s. testem.js not loaded?"
reeteshranjan
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Travis integration - localIdentifier
As described in https://docs.travis-ci.com/user/browserstack/ and https://www.browserstack.com/automate/travisci, when using Selenium, there is a identifier associated with each local connection created, and it is provided in the environment variable BROWSERSTACK_LOCAL_IDENTIFIER and must be included in the settings, in case multiple local connections are used.
The change in this commit takes the ruby selenium webdriver example described in above links, and provides the same steps for this testem browserstack integration. This change has been verified with a Travis build running testem ci for the repository https://github.com/reeteshranjan/browse.js.
Testem browser start timeout
Testem has a default browser start timeout of 30 seconds, which hits few times while trying to run BrowserStack tests using testem. The default setting is being overridden with a timeout of 600 (10 minutes) which should avoid this in most cases.
The error message that pops up when this timeout occurs is the following:
"Browser failed to connect within 30s. testem.js not loaded?"