Add Drengr Runner to UI Testing - #3355
Open
SharminSirajudeen wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Drengr Runner under UI Testing, alphabetically between Cucumber and EarlGrey.
A single XCTest target that hosts a loopback HTTP server inside a UI test bundle. 479 lines of Swift. Three endpoints — status, observe (JPEG screenshot plus accessibility snapshot), and act (tap, swipe, draw, type, hardware button, rotation) — so any language that can make an HTTP request can drive a simulator.
It exists because WebDriverAgent is a large dependency with its own build and host process that breaks on Xcode upgrades, and for driving a simulator by coordinates almost none of it is needed. Physical devices and device clouds still go through Appium/WDA; this replaces it on simulators only.
Apache-2.0. Known limitations are documented in the README rather than omitted (draw_path lifts the finger between segments, type needs a focused field, home is the only wired hardware button, simulators only).