-
Notifications
You must be signed in to change notification settings - Fork 5
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
Parity with testium-driver-sync #4
Conversation
} | ||
|
||
function getterToPropName(propName) { | ||
return propName.replace(/^get([A-Z])/, secondToLowerCase); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should there be a + or * in there? e.g. /^get([A-Z]+)/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if getABC
should become abc
, aBC
, or ABC
. I'd consider that "undefined behavior". I don't think that's an actual case this function handles. E.g. all properties it's concerned with are the ones provided by webdriver, e.g. getText -> text
, getPageTitle -> pageTitle
, etc.
Nice work! |
Parity with testium-driver-sync
browser.getElement
: Throws a clean exception if the element doesn't existbrowser.getElementOrNull
: Same behavior as-sync
'sgetElement
setCookieValue
andgetCookieValue
for parity with-sync
. Those methods aren't part of-sync
but itssetCookie
defaults topath: '/'
which conflicts with howwd
works.Issue outlining where
testium-driver-wd
's API differs fromtestium-driver-sync
: testiumjs/testium-driver-sync#8