Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

chore(protractor): use directConnect locally to speed up tests #14919

Closed

Conversation

gkalpak
Copy link
Member

@gkalpak gkalpak commented Jul 15, 2016

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Chore.

What is the current behavior? (You can also link to an open issue here)
Protractor tests use Selenium Server.

What is the new behavior (if this is a feature change)?
Protractor tests use the ChromeDriver to connect to Chrome directly.
This does not affect e2e tests on Travis or Jenkins.

Does this PR introduce a breaking change?
No.

Please check if the PR fulfills these requirements

Other information:
For me it reduced the execution time from ~130s to ~110s.
It is no big deal, but if it's for free, why not.

@petebacondarwin
Copy link
Contributor

LGTM - merging

@gkalpak gkalpak deleted the chore-protractor-use-directConnect branch July 18, 2016 09:24
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants