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

Find possible bugs #10

Open
jespitiaa opened this issue Mar 27, 2020 · 3 comments
Open

Find possible bugs #10

jespitiaa opened this issue Mar 27, 2020 · 3 comments

Comments

@jespitiaa
Copy link
Collaborator

Test different web applications to find anomalies

@jespitiaa
Copy link
Collaborator Author

Scrolling events cause the test to fail when the webpage does not have scroll bars

@jespitiaa
Copy link
Collaborator Author

Forcing clicks may cause the test to fail when some elements are selected as targets. Usually the elements that induce the errors do not have a natural click response, such as some divs, spans, etc.
Errors can also be caused when partially-visible elements are selected as targets.
Removing {force:true} should do the trick

@jespitiaa
Copy link
Collaborator Author

Apparently, scrolling events do not work well because of the variables curX and curY not changing at the expected time of the execution.
Cypress seems to queue all the events with their parameters before executing, and then, after everything is set, events are actually fired.
For this reason changing the viewport-related variables when executing the corresponding commands, and refer to this variables' values will not work as expected. The variables' values would be the same during the whole execution

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

No branches or pull requests

1 participant