Closed jeffdav closed 1 year ago
I think we should let webdriver-swift be only a UI automation framework and build a higher level UI testing framework on top for features like this
Closing this. The plan is be to stick to representing the webdriver API in webdriver-swift
, and to implement DPI and other more UI testing specific features in an XCUITest
reimplementation built on top of this library.
Arc wrote this extension method for
Element
, and we should consider just doing this for them: