Default web driver changed from Firefox to Chrome#327
Merged
tkaik merged 2 commits intomilestone/chrome-supportfrom Aug 21, 2018
Merged
Default web driver changed from Firefox to Chrome#327tkaik merged 2 commits intomilestone/chrome-supportfrom
tkaik merged 2 commits intomilestone/chrome-supportfrom
Conversation
Adapted RestProxyManager configuration for Selenium Grid setup - added UpgradeNotes entry
malaskowski
approved these changes
Aug 21, 2018
Contributor
malaskowski
left a comment
malaskowski
left a comment
There was a problem hiding this comment.
Could you please update changelog?
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Default web driver changed from Firefox to Chrome. Added RestProxyManager configuration file for local development (on vagrant). Added UpgradeNotes entry to explain the need to change RestProxyManager configuration in new AET version.
Motivation and Context
When some environment is using default settings or when someone starts a new AET instance (e.g. on vagrant), we want the tests to be working on Chrome web driver by default.
Screenshots (if appropriate):
Types of changes
Checklist:
I hereby agree to the terms of the AET Contributor License Agreement.