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

Inconsistencies between -wd and -sync #8

Open
8 tasks
jkrems opened this issue Oct 26, 2015 · 2 comments
Open
8 tasks

Inconsistencies between -wd and -sync #8

jkrems opened this issue Oct 26, 2015 · 2 comments

Comments

@jkrems
Copy link
Member

jkrems commented Oct 26, 2015

  • click had to become clickOn because the former is already a wd method
  • *IsVisible became *IsDisplayed because that's how wd calls it. Not sure if we should ignore this
  • close ("close session") had to become quit because wd already has a close ("close current window")
  • setCookie doesn't default path: '/'. But setCookieValue exists with defaults for path and secure
  • wd only supports top-level custom methods, so assert.isFoo became assertIsFoo
  • getElement throws if the element doesn't exist, getElementOrNull returns null in that case
  • While moving assert.*, assert.httpStatus became assertStatusCode to be consistent with getStatusCode
  • -wd uses a different algorithm for comparing urls with "fuzzy query argument order". Instead of building a regex, it compares the parsed urls.
@EndangeredMassa
Copy link
Member

@jkrems is this still all true?

@jkrems
Copy link
Member Author

jkrems commented Apr 17, 2017

I think most of these remain. I'm not 100% sure though.

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

2 participants