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

Wrong actions result #2453

Open
abudLR opened this issue Mar 13, 2023 · 1 comment
Open

Wrong actions result #2453

abudLR opened this issue Mar 13, 2023 · 1 comment

Comments

@abudLR
Copy link

abudLR commented Mar 13, 2023

Hello, I have a recurring bug, Cerberus often considers actions as passed while they haven't been done, which makes tests crash on another step than the one that is problematic.
According to the screenshots linked with the issue, Cerberus states that it clicked an "Add to basket" button (in dutch) but the button isn't even visible on the screen which makes the rest of the test impossible to run. But the element isn't absent, a scroll is needed to display the element as it's in a lower part of the page.
wrong_action_state

@vertigo17
Copy link
Member

Is that a reproducible issue ?
Is that only on Appium or Selenium also ?
In such cases, the best is to perform a control to secure that expected result occurs. It could happen that Selenium is too fast to trigger the event (depending on how the page is build, sometimes the event occurs before the needed js is loaded to handle it).

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

3 participants