Fix Protractor/Selenium Configuration #79
Merged
Conversation
This file contains 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
…ine seleniumServerJar instead to get selenium running
|
thanks! |
PatrickJS
added a commit
that referenced
this pull request
Sep 22, 2015
Fix Protractor/Selenium Configuration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To get e2e tests running, I had to fix some issues with Protractor/Selenium. First of all I had to adjust the port of the
baseUrlto3000since the webpack dev server is running on this port.Then I ran into an issue in which it was impossible to get the WebDriver session started. This is documented here. The solution by @josefsalyer worked for me, so I suggest to use it in this repo as well.