|
| 1 | +# Protractor support topics |
| 2 | + |
| 3 | +## Supported browsers |
| 4 | + |
| 5 | +### Tests with Protractor test suite (v 4.0.13) |
| 6 | + |
| 7 | +The following are the supported browsers / drivers based on running the |
| 8 | +Protractor test suite. Since the test suite checks only firefox and chrome, |
| 9 | +these are the only browsers reported. |
| 10 | + |
| 11 | +### Current supported browsers / drivers |
| 12 | + |
| 13 | +| selenium standalone | firefox | chromedriver | chrome | |
| 14 | +| ------------------- | ------- | ------------ | ------ | |
| 15 | +| 2.53.1 | 47.0.1 | 2.26 | 54 | |
| 16 | + |
| 17 | + |
| 18 | +### Investigated |
| 19 | + |
| 20 | +| selenium standalone | firefox 47.0.1 | firefox 49.0.1 | |
| 21 | +| ------------------- | -------------- | -------------- | |
| 22 | +| 2.53.1 | pass | fail | |
| 23 | +| 3.0.0 | fail | fail | |
| 24 | + |
| 25 | + |
| 26 | +## Driver providers |
| 27 | + |
| 28 | +There are a couple cases where Protractor launches downloaded binaries |
| 29 | +(from webdriver-manager) without specifying which version to use: |
| 30 | + |
| 31 | +- local driver providers - when no `seleniumAddress`, `directConnect`, saucelabs |
| 32 | + or browser stack configuration is set |
| 33 | +- direct connect - when setting `directConnect` to true |
| 34 | + |
| 35 | +Protractor knows which downloaded binaries to use based on the |
| 36 | +`update-config.json`. The `update-config.json` is written during the `update` |
| 37 | +command and provides the path to the current downloaded version and a list of |
| 38 | +all the binaries previously downloaded. |
| 39 | + |
| 40 | +During the launch of either local driver provider or direct connect, Protractor |
| 41 | +will launch the last downloaded binary. |
0 commit comments