28

Checking the protractor documentation, I see there is a option to run protractor without using Selenium server using directConnect: true flag.

What is the difference between running protractor tests with a selenium server and without a selenium server other than the fact that only Chrome, Firefox are supported for the latter case?

alecxe
  • 462,703
  • 120
  • 1,088
  • 1,195
meteor
  • 2,518
  • 4
  • 38
  • 52

2 Answers2

49

First of all, currently, you have 5 different built-in options/ways to connect to browser drivers:

  1. specify seleniumServerJar to start selenium standalone server locally
  2. specify seleniumAddress to connect to a running selenium server (local or remote)
  3. set sauceUser and sauceKey to connect to Sauce Labs remote selenium server
  4. set browserstackUser and browserstackKey to use remote Selenium Servers via BrowserStack
  5. use directConnect to connect to Chrome or Firefox directly. There are additional chromeDriver and firefoxPath setting that you can use to define custom Chrome driver and Firefox application binary locations.

The first 4 options basically work through a "proxy", a selenium server:

The server acts as proxy between your test script (written with the WebDriver API) and the browser driver (controlled by the WebDriver protocols). The server forwards commands from your script to the driver and returns responses from the driver to your script.

The main reason to automate browsers through an intermediate selenium server as opposed to direct webdriver connect is that selenium server, if acts as a Selenium Grid, allows you to expand/scale your tests across multiple browsers, multiple browsers on multiple systems, see, for instance, Sauce Labs Selenium Grid. FYI, there is also BrowserStack service, that, apart of other features, acts as a selenium server with, similarly to Sauce Labs, enormous amount of different capabilities/configurations - browsers and systems.

The other use case of starting up a selenium server (speaking about option 2) and not using directConnect is that you may have a specific configuration(s) you want your tests to run on. Say, you have a Windows machine with IE 11 on board and Ubuntu with Firefox 35. In this case, you may configure these machines as selenium nodes which would connect to a selenium server/hub.

If you are running your tests locally and your target browsers are Chrome or/and Firefox, use directConnect, your tests would run faster.

But, if you are running your tests locally and need to test against IE, Safari or other browsers, you'd go with options 1-4 (usually 1), since these browsers cannot work in "direct connect" mode.

See also related topics:

Community
  • 1
  • 1
alecxe
  • 462,703
  • 120
  • 1,088
  • 1,195
4

In simple words if directConnect is true then it will run the tests without using selenium server. Where selenium server means a setup similar to Selenium Grid (Hub and node). Running tests via Selenium Server allows you to run tests on remote machine or on your local machine and provides an option to distribute execution load among different nodes. It is also possible to run test on multiple browsers at same time using selenium server.

While directConnect false will run test only on your local installation of FireFox and Chrome. It will run the test on same machine where test codebase exist.

Priyanshu
  • 3,040
  • 3
  • 27
  • 34
  • directConnect is a boolean in the configuration? can you show it? – Alexander Mills Feb 27 '18 at 19:34
  • @AlexanderMills, here is an example: let chromeDriverLocation = process.env.chromedriver; exports.config = { chromeDriver: chromeDriverLocation, directConnect: true, specs: ['spec.js'] }; – JavaGeek Feb 18 '21 at 14:30