Skip to content

Conversation

haoqunjiang
Copy link
Member

  1. By checking for firefox installation, users can save the bandwith of
    downloading the geckodriver package if they don't need it;
  2. By detecting installed Chrome version, even if we failed to closely
    follow up chromedriver's releases, users can still get the correct
    version they need;
  3. By comparing user's Chrome version with the installed chromedriver
    version and output warnings, users can have a basic knowledge of what
    actions to take if they accidentally updated to an incompatible
    version of Chrome.

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Docs
  • Underlying tools
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

Other information:

…ing / before running tests

1. By checking for firefox installation, users can save the bandwith of
downloading the geckodriver package if they don't need it;
2. By detecting installed Chrome version, even if we failed to closely
follow up chromedriver's releases, users can still get the correct
version they need;
3. By comparing user's Chrome version with the installed chromedriver
version and output warnings, users can have a basic knowledge of what
actions to take if they accidentally updated to an incompatible
version of Chrome.
@haoqunjiang haoqunjiang merged commit 0473432 into vuejs:dev Sep 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant