New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox 50 and latest protractor/selenium. Timeout issues. #3750

Closed
inthegarage opened this Issue Nov 17, 2016 · 17 comments

Comments

Projects
None yet
10 participants
@inthegarage

I've decided to see what was happening with Firefox 50, latest selenium and protractor
Here are my versions.

  • Node Version: v5.10.1
  • Protractor Version: 4.0.11
  • Angular Version: 1.4.9
  • Browser(s): Firefox 50
  • Operating System and Version Windows 10
  • Selenium 3.0.1
  • Firefox driver: 0.11.1 (gecko driver)
    When I use the same test framework on Chrome or Internet explorer, everything just runs fine in my test
    However when I use Firefox 50, I get many timeout related errors:

Failed: Error while waiting for Protractor to sync with the page: "[ng:test] http://errors.angularjs.org/1.4.7/ng/test"
Or
Failed: Error while waiting for Protractor to sync with the page: "window.angular is undefined

The place where you get these errors seems to be random.

The tests are the same for all browsers, my capabilities are as follows from the test file:

    capabilities: {
        'browserName': 'firefox',
        marionette : true,
    }

What is the current status of Firefox and Protractor? Is it supported? Do I need any other options or different versions?

@inthegarage inthegarage changed the title from Firfox and to Firefox 50 and latest protractor/selenium. Timeout issues. Nov 17, 2016

@juliemr

This comment has been minimized.

Show comment
Hide comment
@juliemr

juliemr Nov 18, 2016

Member

FireFox support is definitely in flux at the moment. Please see http://www.protractortest.org/#/browser-support - we still recommend firefox 47.

Behind the scenes - we're also still trying to figure out how to support geckodriver with firefox for versions higher than 48.

Member

juliemr commented Nov 18, 2016

FireFox support is definitely in flux at the moment. Please see http://www.protractortest.org/#/browser-support - we still recommend firefox 47.

Behind the scenes - we're also still trying to figure out how to support geckodriver with firefox for versions higher than 48.

@inthegarage

This comment has been minimized.

Show comment
Hide comment
@inthegarage

inthegarage Nov 18, 2016

Hi Julie,

Thanks for the reply. Firefox 50 with the above framework seems much more stable then 49 say and other variants. This seems very close now and my tests nearly worked.
It would appear that there just needs to be some tweaking to do, possibly in the Protractor side, but I'm no expert as to where the problem may actually lie.
Shall I keep this ticket open so we can track progress, or is that mechanism really reflected in the link you provided?

inthegarage commented Nov 18, 2016

Hi Julie,

Thanks for the reply. Firefox 50 with the above framework seems much more stable then 49 say and other variants. This seems very close now and my tests nearly worked.
It would appear that there just needs to be some tweaking to do, possibly in the Protractor side, but I'm no expert as to where the problem may actually lie.
Shall I keep this ticket open so we can track progress, or is that mechanism really reflected in the link you provided?

jferna57 added a commit to jferna57-org/21-points-jhipster that referenced this issue Dec 7, 2016

frederikschubert added a commit to INSIDEM2M/slim that referenced this issue Dec 13, 2016

fix(build): do not run e2e tests for now
There are still issues with newer versions of
firefox. See angular/protractor#3750
@sjelin

This comment has been minimized.

Show comment
Hide comment
@sjelin

sjelin Dec 22, 2016

Contributor

(assigning to you @mgiambalvo because I didn't assign many over issues to you, and I feel like I need to balance)

Contributor

sjelin commented Dec 22, 2016

(assigning to you @mgiambalvo because I didn't assign many over issues to you, and I feel like I need to balance)

@commutecat

This comment has been minimized.

Show comment
Hide comment
@commutecat

commutecat Dec 22, 2016

To mitigate Firefox multi-process architecture incompatibilities with any web testing tools , use Firefox ESR 45.
https://www.mozilla.org/en-US/firefox/45.3.0/releasenotes/

commutecat commented Dec 22, 2016

To mitigate Firefox multi-process architecture incompatibilities with any web testing tools , use Firefox ESR 45.
https://www.mozilla.org/en-US/firefox/45.3.0/releasenotes/

@inthegarage

This comment has been minimized.

Show comment
Hide comment
@inthegarage

inthegarage Dec 22, 2016

Although that certainly tests any software on Firefox, it doesn't test it on 50+, that is what most users will be using and more importantly what most customers will require.
I will raise this issue with Selenium as suggested, although currently the issue(s) seems to be in both products.

Although that certainly tests any software on Firefox, it doesn't test it on 50+, that is what most users will be using and more importantly what most customers will require.
I will raise this issue with Selenium as suggested, although currently the issue(s) seems to be in both products.

@heathkit

This comment has been minimized.

Show comment
Hide comment
@heathkit

heathkit Jan 10, 2017

Member

Firefox 50 has a bug that affects timeouts in webdriver injected scripts. This bug has been fixed, and we should support testing in Firefox 51+

Member

heathkit commented Jan 10, 2017

Firefox 50 has a bug that affects timeouts in webdriver injected scripts. This bug has been fixed, and we should support testing in Firefox 51+

@hymau

This comment has been minimized.

Show comment
Hide comment
@hymau

hymau Mar 24, 2017

I was struggling hard to find a solution to the FF execution and finally got it working today.
Please find the versions which worked on my end.
Mac OSX: Sierra v10.12
FF: 53 beta
Selenium Standalone jar: 3.3.1
Protractor: v 5.1.1
Config file:
{
"browserName": "firefox",
"marionette":true,
}
Hope this helps :)

hymau commented Mar 24, 2017

I was struggling hard to find a solution to the FF execution and finally got it working today.
Please find the versions which worked on my end.
Mac OSX: Sierra v10.12
FF: 53 beta
Selenium Standalone jar: 3.3.1
Protractor: v 5.1.1
Config file:
{
"browserName": "firefox",
"marionette":true,
}
Hope this helps :)

@erved

This comment has been minimized.

Show comment
Hide comment
@erved

erved Aug 1, 2017

Hey ! juliemr,
I am trying to run protractor on firefox 47 but it doesn't make any sense.

erved commented Aug 1, 2017

Hey ! juliemr,
I am trying to run protractor on firefox 47 but it doesn't make any sense.

@inthegarage

This comment has been minimized.

Show comment
Hide comment
@inthegarage

inthegarage Aug 1, 2017

@erved Firefox47-51ish doesn't work with protractor. Don't even bother trying. Either use Firefox ESR 45. or the latest version.

@erved Firefox47-51ish doesn't work with protractor. Don't even bother trying. Either use Firefox ESR 45. or the latest version.

@wswebcreation

This comment has been minimized.

Show comment
Hide comment
@wswebcreation

wswebcreation Aug 1, 2017

Collaborator

@erved ,

Please don't address questions directly to members. We all try to check the issue list.

By the way. FF 47 should work, only with the old driver, secondly also with Selenium 2.53 and not with Selenium 3.x.

Collaborator

wswebcreation commented Aug 1, 2017

@erved ,

Please don't address questions directly to members. We all try to check the issue list.

By the way. FF 47 should work, only with the old driver, secondly also with Selenium 2.53 and not with Selenium 3.x.

@samsul-kabir

This comment has been minimized.

Show comment
Hide comment
@samsul-kabir

samsul-kabir Aug 3, 2017

Hi there,

I have tried different version of firefox and unfortunately none of them worked. Everytime i running my code, its throwing the following error:

[15:41:09] E/launcher - Unable to find a matching set of capabilities
Build info: version: '3.4.0', revision: 'unknown', time: 'unknown'
System info: host: 'trv2457.local', ip: '2001:920:1841:10:ac95:6fb8:a651:b9d5', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.12.6', java.version: '1.8.0_111'
Driver info: driver.version: FirefoxDriver
remote stacktrace: stack backtrace:
   0:        0x10aad754e - backtrace::backtrace::trace::hc694823f3e7463c0
   1:        0x10aad76ec - backtrace::capture::Backtrace::new::h23089c033eded8f0
   2:        0x10aa6f3af - geckodriver::marionette::MarionetteHandler::create_connection::hfc7af8bf299cf57b
   3:        0x10aa4a707 - _$LT$webdriver..server..Dispatcher$LT$T$C$$u20$U$GT$$GT$::run::h03bbbfe904a992bd
   4:        0x10aa30c97 - std::panicking::try::do_call::he6fd7abc59b6b346
   5:        0x10abf44ba - __rust_maybe_catch_panic
   6:        0x10aa4100c - _$LT$F$u20$as$u20$alloc..boxed..FnBox$LT$A$GT$$GT$::call_box::h8e002f7c448fbabb
   7:        0x10abf0684 - std::sys::imp::thread::Thread::new::thread_start::hba7593f2e1f1beb1
   8:     0x7fff9c77093a - _pthread_body
   9:     0x7fff9c770886 - _pthread_start

Version that I have

protractor@5.1.2
selenium-webdriver@3.0.1
Mac os x: 10.12.6

Hi there,

I have tried different version of firefox and unfortunately none of them worked. Everytime i running my code, its throwing the following error:

[15:41:09] E/launcher - Unable to find a matching set of capabilities
Build info: version: '3.4.0', revision: 'unknown', time: 'unknown'
System info: host: 'trv2457.local', ip: '2001:920:1841:10:ac95:6fb8:a651:b9d5', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.12.6', java.version: '1.8.0_111'
Driver info: driver.version: FirefoxDriver
remote stacktrace: stack backtrace:
   0:        0x10aad754e - backtrace::backtrace::trace::hc694823f3e7463c0
   1:        0x10aad76ec - backtrace::capture::Backtrace::new::h23089c033eded8f0
   2:        0x10aa6f3af - geckodriver::marionette::MarionetteHandler::create_connection::hfc7af8bf299cf57b
   3:        0x10aa4a707 - _$LT$webdriver..server..Dispatcher$LT$T$C$$u20$U$GT$$GT$::run::h03bbbfe904a992bd
   4:        0x10aa30c97 - std::panicking::try::do_call::he6fd7abc59b6b346
   5:        0x10abf44ba - __rust_maybe_catch_panic
   6:        0x10aa4100c - _$LT$F$u20$as$u20$alloc..boxed..FnBox$LT$A$GT$$GT$::call_box::h8e002f7c448fbabb
   7:        0x10abf0684 - std::sys::imp::thread::Thread::new::thread_start::hba7593f2e1f1beb1
   8:     0x7fff9c77093a - _pthread_body
   9:     0x7fff9c770886 - _pthread_start

Version that I have

protractor@5.1.2
selenium-webdriver@3.0.1
Mac os x: 10.12.6
@inthegarage

This comment has been minimized.

Show comment
Hide comment
@inthegarage

inthegarage Aug 3, 2017

@samsul-kabir The web driver looks a little out of date, check here: http://www.seleniumhq.org/download/
Protractor part is up-to-date.

inthegarage commented Aug 3, 2017

@samsul-kabir The web driver looks a little out of date, check here: http://www.seleniumhq.org/download/
Protractor part is up-to-date.

@samsul-kabir

This comment has been minimized.

Show comment
Hide comment
@samsul-kabir

samsul-kabir Aug 3, 2017

@inthegarage I have update webdriver using following command:

webdriver-manager update

what would be the best way to update it?

@inthegarage I have update webdriver using following command:

webdriver-manager update

what would be the best way to update it?

@inthegarage

This comment has been minimized.

Show comment
Hide comment
@inthegarage

inthegarage Aug 3, 2017

That's probably the best way, you can check if it matches the version on the list. You'd suspect its probably a Mac issue.

That's probably the best way, you can check if it matches the version on the list. You'd suspect its probably a Mac issue.

@wswebcreation

This comment has been minimized.

Show comment
Hide comment
@wswebcreation

wswebcreation Aug 3, 2017

Collaborator

Hi @samsul-kabir

Does it work with a the simple example script from protractor on FireFox? I don't have any issues here with firefox.

Collaborator

wswebcreation commented Aug 3, 2017

Hi @samsul-kabir

Does it work with a the simple example script from protractor on FireFox? I don't have any issues here with firefox.

@kalesha67

This comment has been minimized.

Show comment
Hide comment
@kalesha67

kalesha67 Oct 24, 2017

Hi,

any solution to below error:

E/launcher - Error: Error: The wires.exe executable could not be foun
d on the current PATH. Please download the latest version from https://developer
.mozilla.org/en-US/docs/Mozilla/QA/Marionette/WebDriver and ensure it can be fou
nd on your PATH.

Hi,

any solution to below error:

E/launcher - Error: Error: The wires.exe executable could not be foun
d on the current PATH. Please download the latest version from https://developer
.mozilla.org/en-US/docs/Mozilla/QA/Marionette/WebDriver and ensure it can be fou
nd on your PATH.

@inthegarage

This comment has been minimized.

Show comment
Hide comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment