CODEWITHSUNDEEP
angularjasminewebdriverprotractor
vasundhara
vasundhara

Reputation: 109

Unable to run "Protractor test scripts in Firefox browser" for "angular 4 applicaiton"

I am new to Protractor tool. I am unable to run my Test script in multiple browsers, only in Chrome.

I am using

  1. Node: v6.11.3
  2. NPM: 3.10.10
  3. Protractor: 5.1.2

I need to automate the Angular 4 application using Visual studio code IDE. I added "multi capabilities" option my Protractor.conf.js as below.

multiCapabilities:[{
  'browserName' : 'chrome'},
  {'browserName':'firefox'}]

Test script was running in only chrome browser, For firefox it is displaying below error

[11:47:37] I/launcher - 0 instance(s) of WebDriver still running
[11:47:37] I/launcher - firefox #01 failed with exit code: 135
[11:47:37] I/launcher - chrome #11 passed
[11:47:37] I/launcher - overall: 1 process(es) failed to complete
[11:47:37] E/launcher - Process exited with error code 100

How to setup and run test scripts parallel in multiple browsers?

Upvotes: 0

Views: 1034

Answers (2)

HaC
HaC

Reputation: 950

For Firefox v48 and above, you'll also need to add marionette capability:

multiCapabilities:[
  {'browserName' : 'chrome'},
  {'browserName':'firefox',
   'marionette': true}]

UPDATE: There is a open issue #4253 introduced in Protractor 5.1.1 . The workaround is to manually replace directConnect with seleniumAddress and manually start webdriver-manager as specified in the bug:

The solution is to use selenium standalone when testing with Firefox. The latest version of the selenium standalone server is compatible with Protractor's selenium JS bindings and with geckodriver. You can update and launch the standalone server with

webdriver-manager update
webdriver-manager start

and set seleniumAddress: http://localhost:4444/wd/hub

Upvotes: 1

Ernst Zwingli
Ernst Zwingli

Reputation: 1422

I can think of several reasons for your error. Here some suggestions:

By default Protractor only updates Chrome driver. So please try webdriver-manager update as described here.

If that did not do the trick, check if your firefox-driver is at its expected location. Read more about here

If you still have no luck, you might have catched an incompatibility between the current Firefox Driver and the latest Firefox-Browser (i.e. if you beta-test new firefox browser-version). Read about the same issue for Chrome here. It will work the same way for Firefox, of course.

Upvotes: 0

Related Questions