Repository navigation
feat(runner): tap, swipe and fill actions for mobile runners (AGE-4855) - #1638
Merged
Merged
Conversation
Erzhan Torokulov (erzhtor)
force-pushed
the
age-4855-act-mobile-targets
branch
from
September 30, 2026 12:28
af112c1 to
f4ea8de
Compare
Erzhan Torokulov (erzhtor)
changed the title
0.72.0 never published; 0.73.0 carries the mobile runner actions plus issue.create maintenance reports and run.get needsReview.
Erzhan Torokulov (erzhtor)
marked this pull request as ready for review
October 1, 2026 07:21
Goran Gajic (gorangajic)
approved these changes
Oct 1, 2026
Yurij Mikhalevich (yurijmikhalevich)
approved these changes
Oct 1, 2026
Atchyut Preetham Pulavarthi (theonly1me)
left a comment
Atchyut Preetham Pulavarthi (theonly1me)
left a comment
Member
There was a problem hiding this comment.
Oops forgot posting the feedback
| | `qawolf run triage` | read | Prototype. Ask Jev, a TypeSafe System One model, whether a flow failure in a run is a bug in the product or a test that needs maintenance. Compares the failing attempt with the flow's last passing run in the same environment. Records nothing. | | ||
| | `qawolf runner act` | write | Perform one raw action on a runner's screen: click, double_click, scroll, move, drag, keypress, navigate or type. Use - to read a whole action as JSON from stdin. On a mobile runner only click (button left), drag and type have a touchscreen equivalent; the rest answer action-not-supported-on-mobile | | ||
| | `qawolf runner act` | write | Perform one raw action on a runner's screen. A browser runner takes click, double_click, scroll, move, drag, keypress, navigate and type; a mobile runner takes tap, swipe, fill and type. A browser runner answers mobile actions with action-not-supported-on-browser; a mobile runner answers the other browser actions with action-not-supported-on-mobile. Use - to read a whole action as JSON from stdin | | ||
| | `qawolf runner actions` | write | Perform a sequence of up to ten raw actions on a runner's screen in one request, as a JSON array of the same actions `runner act` takes. Use - to read the array from stdin. Actions run back to back, so batch only steps whose targets are on the screen you last saw, and end the sequence at the step that changes the page. Each result carries an effect: performed, not-performed, or unknown when the runner stopped answering and the action may have landed | |
There was a problem hiding this comment.
runner actions rejects tap, swipe and fill, so it no longer takes the same actions as runner act. I think we should update the description in actions.register.ts and regenerate this table and the help snapshots.
Contributor
Author
There was a problem hiding this comment.
TIL about runner actions, thanks. Fixed the other way around in #1642 to make runner actions to also accept the mobile actions too. Will land once api-contracts 0.74.0 publishes, e.g. https://github.com/qawolf/platform/pull/34509
4 tasks done
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
4 participants
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.
Relates to AGE-4855. Platform side: qawolf/platform#34398 (merged, published in
@qawolf/api-contracts0.73.0).Overview of Changes
qawolf runner actgets the new mobile actions from the platform contract:tap:--x/--y, or--selector(+ optional--strategy)swipe:--from x,y --to x,y, optional--duration-ms(max 10000)fill:--selector --text, replaces the field's valuetypestill works on both families. On mobile,click/dragstill work but are deprecated in favour oftap/swipe(removal: AGE-5384). A browser runner refuses the mobile actions withaction-not-supported-on-browser, exit code 2.The CLI only maps flags onto the action; the published
runnerActionSchemavalidates it.runner actionssequences stay browser-only. In the SDK types,ActRequest.actionwidens fromBrowserActiontoRunnerAction, so nothing that was valid breaks.Also:
actexamples and flag parsers moved toactExamples.tsandflagValues.tsto stay under the file-length lint. Therun triagerow dropped fromSKILL.md, theissue createandneedsReviewtext in the skill docs, and the--effort/--reasonflags inflagSpecs.union.test.tsall come from the contracts bump.Testing
Ran against published 0.73.0:
typecheck,lint,format:check,knipandtestpass, except 3 keychain tests that also fail onmainon this machine.Checklist