Whats are the Protractor Supported versions of Fir

问题:

Whats are the Protractor Supported versions of Firefox, IE and Safari?

My test does not run in Firefox latest version.

回答1:

@High level Protractor is just a wrapper around webdriver. It depends on browser versions you want to test en the webdrivers for that browsers you have downloaded with webdriver-manager as said by @alecxe

Currently there are some known issues with the webdrivers that can also be found on the Protractor GitHub:

• Firefox latest has problems with Angular2 apps, see this link, as far as I can remember Protractor worked till Firefox 47, it broke due to problems in de webdriver of Firefox from version 48-50 and it started working from 51, but not for Angular 2
  • IE11 works
  • Microsoft Edge, see this, as far as I can see still not stable on version 14
  • Safari 9, works, but it's with the old Safari Driver, it misses a lot of user interactions like Tabs, mouse events and so on
  • Safari 10, I've heard that it works with the latest version of the Safari webdriver, don't heave experience with it, see also here for a guy who had problems with it but got it working.
  • Chrome, should work with all latest versions if you always keep you ChromeDriver up-to-date

Hope this gives you a good idea

回答2:

Protractor depends on the webdriver-manager package which now, since version 12.0.0, installs the latest versions of selenium-webdriver, iedriver, chromedriver and geckodriver.

Then, to determine which browser versions are supported, you need to see what driver version was installed by the webdriver-manager:

$ webdriver-manager status

and then look up what browser versions your installed driver version supports.

---

My test does not run in Firefox latest version.

In your case, you might be experiencing this problem:

Webdriver-manager will now by default grab the latest versions of all binaries (standalone, chromedriver, iedriver, gecko driver). Use the --versions.(binary name) to pin to a specific version. Selenium standalone 3.0.1 has a bug which prevents it from working with any version of FireFox. We have tested version 3.0.0-beta4 and know that it works with FireFox 51, and we expect that the 3.0.2 release will also work.

Which currently means that you should be able to fix it by running:

$ webdriver-manager update

Or, you may also try the directConnect mode.