Protractor test is not starting on Firefox #886
Comments
|
Silly question, but do you have firefox installed on your machine? What sort of output do you get? |
|
Hi Julie I do, I have got version 29 installed, the funny thing that I am not getting any error, just firefox passed and then returns. |
|
Any output from the selenium standalone? |
|
Nothing that is the funny thing, does not do anything |
|
Hi I found the problem with firefox, basically my protractor config was not using any webdriver server setting but was using the default server, this way was quite handy since did not have start selenium by my self In order to fix this issue I am starting selenium server by myself specifying firefox and chrome drivers java -jar "C:\Users%USERNAME%\AppData\Roaming\npm\node_modules\protractor\selenium\selenium-server-standalone-2.42.1.jar" -Dwebdriver.chrome.driver="C:\Users%USERNAME%\AppData\Roaming\npm\node_modules\protractor\selenium\chromedriver.exe" -Dwebdriver.firefox.bin="C:\Users%USERNAME%\AppData\Local\Mozilla Firefox\firefox.exe" |
|
Ah, OK. The problem was that your firefox is not in the default location (as described on the FirefoxDriver page). Glad you got it sorted out! |
|
I have a same problem , firefox is installed in the default location "c:\Program Files\Mozilla Firefox\firefox.exe" in windows XP, capabilities: { Using the selenium server at http://127.0.0.1:4444/wd/hub Process finished with exit code 1 my test script is not execute. Please help me note : In chrome it's working fine |
|
Selenium console should tell you what is going in on with it, try to start you own selenium in order to see selenium error messages |
|
When I run my protractor scripts on Firefox, firefox window is opened but failed to open the target URL and getting the following error: c:\node_modules\protractor\node_modules\selenium-webdriver\http\util.js:89 Process finished with exit code 1 Can someone please help me out with this? Regards, |
|
Hi @nareshsurya! I recently encountered the same error as you. The quick fix solution for me was to uninstall Firefox 47 and downgrade to Firefox 36. You can find older versions of Firefox here: I'm using selenium-webdriver 2.47.0. I'm not sure which is the latest version of Firefox that is supported, but just wanted to give you a quick fix at the moment! Perhaps someone can please expand upon this! Thank you! |
|
@b-mcrae I love you!! I have been stumped on this for a few hours. My tests were working fine yesterday but when I ran them today they weren't. I guess Firefox updated somewhere in between. |
|
The firefox browser pops up but there is no response after that. The url doesn't get updated nor anything. After the timeout it would close the browser and tests abort. Please find below the logs. Any suggestion would be helpful. Steps followed.
/usr/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:113 From: Task: WebDriver.createSession() |
|
Any solution to the last error? I am experiencing the same! |
|
Protractor is running on Firefox I am using FireFox v44.01, with following settings:- protractor.conf.js and its running fine with Firefox. |
|
What would be the equivalent of this on a mac? I tried, but it didn't work Error |
|
Locate where an executable of firefox is coming from the filesystem and write the fullpath. |
|
Mac OSX 10.10.5 I'm having the same problem with Firefox launching, never navigating to the url, not running any tests, then timing out. Everything works fine in Chrome 55.0.2883.95 (64-bit). I'm following the protractor tutorial, and Step 3 asks me to add Firefox to conf.js: Here is the output when I do In the output above, there is this: I don't know if that's causing a problem. Below is the output in another terminal window when I try to run the tests: m-ajitabh's solution didn't work for me. You can get the path to your firefox executable this way:
I didn't expect m-ajitabh's solution to work because selenium has no problem launching Firefox, so it knows where the firefox executable is located--selenium just seems incapable of driving Firefox. I also checked the selenium docs for the allowed keys in capabilities, so I tried this: ...and I got the same result. I just noticed there was some additional output in the |
|
Guys, I have clearly mentioned above Firefox browser v44.01. |
|
This is an ancient issue, and unrelated to the Firefox woes of the modern era. Please see #3823. The underlying issue is the version of Selenium that Protractor uses. Protractor 4 uses selenium 2.53, and only supports Firefox 47 or older. Protractor 5 can work with Firefox 50, but only with selenium 3.0.0-beta4. Also, Firefox 50 has a bug that might affect Protractor testing, so using the 51 beta is recommended. Protractor 5.1 will support using Firefox 51 with |
|
Guys,
Running automation in firefox has some issues with the different versions
of different framework.
I am running my automation on chrome and it works perfect.
I have also executed my automation suites on firefox, but having older
version of firefox there are some bugs with the design of angular js app
which I was executing.
I setup the chrome as a base and now I am happy.
I do manual testing on firefox for further test.
Thanks
Ajitabh Ranjan
Mob: 9430331985
…On Sat, Jan 21, 2017 at 1:23 PM, mgiambalvo ***@***.***> wrote:
This is an ancient issue, and unrelated to the Firefox woes of the modern
era. Please see #3823 <#3823>.
The underlying issue is the version of Selenium that Protractor uses.
Protractor 4 uses selenium 2.53, and only supports Firefox 47 or older.
Protractor 5 can work with Firefox 50, but only with selenium 3.0.0-beta4.
Also, Firefox 50 has a bug that might affect Protractor testing, so using
the 51 beta is recommended. Protractor 5.1 will support using Firefox 51
with directConnect.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#886 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOad5wcRQIzDdsV33zGYnNKGS3rod9aUks5rUbmRgaJpZM4CAL2g>
.
|
|
Hello All, I am having same issue with latest Firefox version 52.0 32bit when I give directConnect: true nothing works seems like 2 firefox tabs are opened and test fails. But when I start selenium standalone server with gecko driver location and remove directConnect then it works fine. |
|
Update your protractor and try again.
Thanks
Ajitabh Ranjan
Mob: 9430331985
…On Wed, Mar 15, 2017 at 9:59 AM, Rahul Raut ***@***.***> wrote:
Hello All,
I am having same issue with latest Firefox version 52.0 32bit when I give
directConnect: true nothing works seems like 2 firefox tabs are opened and
test fails.
[09:54:22] Using gulpfile D:\projects\GIT hub\gulp-protractor fork\example\gulpfile.js
[09:54:22] Starting 'webdriver_update'...
[09:54:24] I/update - chromedriver: file exists D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\node_modules\webdriver
-manager\selenium\chromedriver_2.28.zip
[09:54:24] I/update - chromedriver: unzipping chromedriver_2.28.zip
[09:54:24] I/update - chromedriver: chromedriver_2.28.exe up to date
[09:54:24] I/update - selenium standalone: file exists D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\node_modules\we
bdriver-manager\selenium\selenium-server-standalone-3.3.1.jar
[09:54:24] I/update - selenium standalone: selenium-server-standalone-3.3.1.jar up to date
[09:54:26] I/update - geckodriver: file exists D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\node_modules\webdriver-
manager\selenium\geckodriver-v0.15.0.zip
[09:54:26] I/update - geckodriver: unzipping geckodriver-v0.15.0.zip
[09:54:26] I/update - geckodriver: geckodriver-v0.15.0.exe up to date
[09:54:26] Finished 'webdriver_update' after 3.91 s
[09:54:26] Starting 'protractor'...
[09:54:27] W/driverProviders - Using driver provider directConnect, but also found extra driver provider parameter(s): seleniumAddress
[09:54:27] I/launcher - Running 1 instances of WebDriver
[09:54:27] I/direct - Using FirefoxDriver directly...
[09:54:34] E/launcher - Unable to parse new session response: {"value": {"sessionId":"2ae0d0d4-bd6e-4683-bcd7-adccf83e66dd","value":{"a
cceptInsecureCerts":false,"browserName":"firefox","browserVersion":"52.0","moz:accessibilityChecks":false,"moz:processID":31788,"moz:pr
ofile":"C:\\Users\\Rahul\\AppData\\Local\\Temp\\rust_mozprofile.nMy4w0qmOZqL","pageLoadStrategy":"normal","platformName":"windows_nt","
platformVersion":"10.0","rotatable":false,"specificationLevel":0,"timeouts":{"implicit":0,"page load":300000,"script":30000}}}}
[09:54:34] E/launcher - WebDriverError: Unable to parse new session response: {"value": {"sessionId":"2ae0d0d4-bd6e-4683-bcd7-adccf83e6
6dd","value":{"acceptInsecureCerts":false,"browserName":"firefox","browserVersion":"52.0","moz:accessibilityChecks":false,"moz:processI
D":31788,"moz:profile":"C:\\Users\\Rahul\\AppData\\Local\\Temp\\rust_mozprofile.nMy4w0qmOZqL","pageLoadStrategy":"normal","platformName
":"windows_nt","platformVersion":"10.0","rotatable":false,"specificationLevel":0,"timeouts":{"implicit":0,"page load":300000,"script":3
0000}}}}
at WebDriverError (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\lib\error.js:27:5)
at doSend.then.response (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\lib\http.js:445:19)
at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()
at Function.createSession (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\lib\webdriver.js:777:24)
at Function.createSession (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\firefox\index.js:640:55)
at Direct.getNewDriver (D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\lib\driverProviders\direct.ts:112:25)
at Runner.createBrowser (D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\lib\runner.ts:225:39)
at q.then.then (D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\lib\runner.ts:391:27)
at _fulfilled (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:834:54)
at self.promiseDispatch.done (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:863:30)
at Promise.promise.promiseDispatch (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:796:13)
at D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:556:49
at runSingle (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:137:13)
[09:54:34] E/launcher - Process exited with error code 199
{ [Error: protractor exited with code 199]
message: 'protractor exited with code 199',
showStack: false,
showProperties: true,
plugin: 'gulp-protractor',
__safety: { toString: [Function: bound ] } }
But when I start selenium standalone server with gecko driver location and
remove directConnect then it works fine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#886 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOad5-VahANDTXAuEHBPEaUo-ymmeOW8ks5rl2kigaJpZM4CAL2g>
.
|
|
It is latest one 5.1.1 |
|
I am not using the gulp to run the protector.
I am using the protractor directly with firefox configuration and it is
running.
How have you configured firefox????
…On Mar 16, 2017 1:00 AM, "Rahul Raut" ***@***.***> wrote:
It is latest one 5.1.1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#886 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOad53VXnGkxDg9j044VAjqtkkeorfQqks5rmDxZgaJpZM4CAL2g>
.
|
|
Not able to Run Protractor Test on Firefox browser Eclipse raised these issue while running test on firefox
|
|
Can you provide more info, like which version:
|
|
Yeah sure! |
|
@makwanaparth94 I ran into this issue while testing with protractor too. The problem was that firefox lost focus, because of me fiddeling around while protractor was running. When I left it do its thing everything went well. |
I have got a set of test that run fine on chrome but when I change the capabilities browserName from chrome to firefox don't even get a error info
Before
capabilities: {
'browserName': 'chrome',
'chromeOptions': { args: ['--test-type', 'show-fps-counter=true'] }
},
//After
capabilities: {
'browserName': 'firefox'
},
The text was updated successfully, but these errors were encountered: