You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
Copy file name to clipboardexpand all lines: docs/server-setup.md
+34
Original file line number
Diff line number
Diff line change
@@ -108,3 +108,37 @@ Protractor can test directly against Chrome and Firefox without using a Selenium
108
108
-`directConnect: true` - Your test script communicates directly Chrome Driver or Firefox Driver, bypassing any Selenium Server. If this is true, settings for `seleniumAddress` and `seleniumServerJar` will be ignored. If you attempt to use a browser other than Chrome or Firefox an error will be thrown.
109
109
110
110
The advantage of directly connecting to browser drivers is that your test scripts may start up and run faster.
111
+
112
+
Re-using an Existing WebDriver
113
+
------------------------------
114
+
115
+
The use case for re-using an existing WebDriver is when you have existing
116
+
`selenium-webdriver` code and are already in control of how the WebDriver is
117
+
created, but would also like Protractor to use the same browser, so you can
118
+
use protractor's element locators and the rest of its API. This could be
119
+
done with the `attachSession` driver provider, but the `attachSession` API is
120
+
being removed in `selenium-webdriver` 4.0.0.
121
+
122
+
Instead of a protractor config file, you create a config object in your test
123
+
setup code, and add your already-created WebDriver object and base URL.
0 commit comments