Skip to content
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

[bug] firefox version > 47 + Gecko driver + browserstack #1539

Closed
Nouxx opened this issue Nov 7, 2017 · 7 comments
Closed

[bug] firefox version > 47 + Gecko driver + browserstack #1539

Nouxx opened this issue Nov 7, 2017 · 7 comments

Comments

@Nouxx
Copy link
Contributor

Nouxx commented Nov 7, 2017

Hello,

There is a unexpected issue in one of the Cerberus campaign. We have one action set to 'click' on a element selected using xpath :

image

But running this campaign, this action seems to be executed as a 'wait' :

image

The xpath selection doesn't seem to cause any problem but the click is not done which make the following steps fail.

Any ideas ?
Thanks

@MowglieRed
Copy link
Collaborator

it seems that it concerns only browser stack.
at least optimize the error message

@Nouxx
Copy link
Contributor Author

Nouxx commented Dec 5, 2017

Update :

  • Workaround : add 'wait' action (2 seconds maximum) to allow element to be properly charged

  • Suggestion : for every click action, force (depending on the application / campaign) a verifiyElementClickable control on the triggered element. This could could improve the reliability of the testcases and stay user friendly. However, the impact of such change has to be investigated

@ryltar
Copy link
Member

ryltar commented Dec 12, 2017

it concerns only browser stack firefox version <= 47.
if browserStack Firefox version > 47 , we have this error and double click which not work due to mouseMoveTo error, same as keypress

@ryltar
Copy link
Member

ryltar commented Dec 12, 2017

firefox version > 47 need marionette (gecko driver). By default, selenium is in 2.x version and don't need a gecko driver in browserStack

@nicodeur nicodeur changed the title Action 'click' executed as 'wait' [bug] firefox version > 47 + Gecko driver + browserstack Dec 13, 2017
@ryltar
Copy link
Member

ryltar commented Dec 13, 2017

it seems that the problem occured with browserstack firefox version between 48 and 58. Waiting firefox 59 version to test.

Problem is due to mouseToMoveToElement is not suported yet by gecko. Click, key press and double clic use mouse

See SeleniumHQ/selenium#3808
And mozzila issue https://bugzilla.mozilla.org/show_bug.cgi?id=1385476

@vertigo17
Copy link
Member

@ryltar , we still need to better handle the error message to make it clear that it failed to find the element.
Considering that the issue is intermittent from selenium, I also think we need to find a way to make it more robust at Cerberus level by an automatic retry. We can try to loop 3 time until object is not null. When issue is fixed on Selenium/Gecko side that will no longuer be used but for 48 to 58 version, that will improve the result.

@ryltar
Copy link
Member

ryltar commented Dec 13, 2017

The problem of click which is transformed into a wait is solved by using an Action object like selenium docs say. I don't have yet push on github

On browserStack firefox only, keypress, double click and click are not working due to firefox version. Selenium say that MouseMouveTo operation is not supported but it seems that in firefox 59, this problem is solved. Retrying click with a loop will not solved the problem because of MouseMouveTo

A little workaround trick is to set the version of firefox to 47

It's a very stange problem because on my localhost, i tried with the same gecko , selenium and firefox version and all action are supported

Maybe just a problem with browserstack firefox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants