@SevInf do you think implementing this functionality as plugin is the best way?
I was thinking, maybe it should be configurable by option in .gemini.yml (queryType, for example) and maybe (not sure if needed), it could be made possible to override it specifically in methods?

Possible selenium queries in wd are:

elementByClassName(value, cb) -> cb(err, element)
elementByCssSelector(value, cb) -> cb(err, element)
elementById(value, cb) -> cb(err, element)
elementByName(value, cb) -> cb(err, element)
elementByLinkText(value, cb) -> cb(err, element)
elementByPartialLinkText(value, cb) -> cb(err, element)
elementByTagName(value, cb) -> cb(err, element)
elementByXPath(value, cb) -> cb(err, element)
elementByCss(value, cb) -> cb(err, element)
elementByIosUIAutomation(value, cb) -> cb(err, element)
elementByAndroidUIAutomator(value, cb) -> cb(err, element)
elementByAccessibilityId(value, cb) -> cb(err, element)

and obviously lots of them are interchangeable by css/sizzle (className, CssSelector, Id…)

Maybe it's just more useful to implement those step-by-step in a core gemini, and made configurable, with default as css selectors / sizzle (for backward compatibility and as most capable one) ?

Uh oh!

Plugins API: ability to add query methods #173

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions