-
Notifications
You must be signed in to change notification settings - Fork 21
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
element position #2
Comments
Looking closer at this one, for x-axis, it's very likely that chrome's scrollbar throwing off the expected result. |
Working closer with this, there are several factors that affect the specific x/y position of an element and it will vary between browsers and environments. We may need to change the tests from the original webdriverio/cucumber-boilerplate numbers to what happens to fit our CI environment. Further, as we develop cross-browser testing, it may be apt to make a test that implements something like 'between x1 and x2 on the <> axis' |
This may even be a problem to get the tests to agree with one another... Between one build to the next, the element position seems like it can vary for some reason. Perhaps there is a race condition. |
Because the core problem remaining is simply related to testing and the element position actually appears to, in fact, be reported correctly, I'll close this issue. May be reopened as another issue for improving tests. |
Appears to be some issues with detecting element position on the x/y axes. Not sure the root cause.
Failing scenarios
Test output for failing scenarios
The text was updated successfully, but these errors were encountered: