Repository navigation
feat(robot): add native Robot Framework support - #1295
Open
kirkbrauer wants to merge 7 commits into
Open
kirkbrauer wants to merge 7 commits into
kirkbrauer wants to merge 7 commits into
Conversation
Contributor
|
Important Review skippedToo many files! This PR contains 175 files, which is 75 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry.
|
kirkbrauer
force-pushed
the
claude/robot-framework-integration-aad017
branch
2 times, most recently
from
November 4, 2026 15:58
23b616c to
62a743f
Compare
mangelajo
force-pushed
the
feat/appium-ui-automation
branch
from
November 11, 2026 08:34
31e4432 to
0680276
Compare
Add jumpstarter-robot, which turns an exporter's drivers into Robot Framework keywords and manages leases from Robot Framework runs. - Keywords for every driver with no driver changes: each driver is a jumpstarter_robot.Driver library whose keywords come from its client class, prefixed with the driver's path (dut.power -> Dut Power On). - `jmp robot generate` (also `jmp-robot`) writes a client resource from robot.toml [tool.jumpstarter.client], so RobotCode and the language server complete every keyword without a lease. `--capture` inside `jmp shell` picks the client from the shell's lease and labels. - Leases, as in the Python helper: attach to a lease created outside the run (JMP_LEASE, or the client's lease with the same selector), run inside `jmp shell`, or call `Acquire Lease`. Local mode serves an exporter config in-process. - Keyword sets for consoles, driver contexts and streams, SSH (SSHLibrary), ADB, iOS and Appium (AppiumLibrary with the lease's certificate verified), port forwards for remote libraries, testbeds as YAML variable files, and pabot parallel runs. - Driver authors can curate keywords with jumpstarter.client.decorators .robot (keyword, not_keyword, library); the Click helpers move to jumpstarter.client.decorators.cli with the old imports kept. - Core: cancel server streams when a streaming call stops early, and add resolve_root_child. Examples in python/examples/robot (basic, multi-dut, lab, zero-config, remote-library, linux-ssh, mobile) run in local mode, and the docs gain a Robot Framework guide and reference section. Assisted-by: Claude:claude-opus-5.5 Signed-off-by: Kirk Brauer <kirkebrauer@gmail.com>
jumpstarter-cli does not depend on jumpstarter-robot, so `jmp robot` is added only when it is installed and ty cannot resolve the import in the package's own environment. Assisted-by: Claude:claude-opus-5.5 Signed-off-by: Kirk Brauer <kirkebrauer@gmail.com>
…cation Start Appium serves a target and returns its url and capabilities, which AppiumLibrary's own Open Application takes as-is. This drops the custom Open Appium Application and Get Appium Target keywords, the per-driver shortcut, and the session bookkeeping behind them, along with the direct Appium-Python-Client and Selenium pins. Assisted-by: Claude:claude-opus-5.5 Signed-off-by: Kirk Brauer <kirkebrauer@gmail.com>
Device Hub sessions now take the same capabilities and tokens as the exporter's Appium, with tokens from the Device Hub target itself. Upload App therefore uploads through a running server named by its driver path or alias, and falls back to the Appium driver as before. The docs no longer say Device Hub sessions take local app paths. Assisted-by: Claude:claude-opus-5.5 Signed-off-by: Kirk Brauer <kirkebrauer@gmail.com>
In-process Robot Framework runs can leave the root logger above WARNING, which left caplog empty on the Linux CI runner. Assisted-by: Claude:claude-opus-5.5 Signed-off-by: Kirk Brauer <kirkebrauer@gmail.com>
main removed pytest-asyncio and pytest-anyio when it finished moving to anyio (#1267): anyio's own pytest plugin runs the async tests, and --strict-markers rejects @pytest.mark.asyncio. jumpstarter-robot has no async tests, so the two dev dependencies were unused. Relock with the pinned uv. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018WEcV1TcwVWwQNggRGywjU
kirkbrauer
force-pushed
the
claude/robot-framework-integration-aad017
branch
from
November 15, 2026 20:55
4b8c9ed to
e9d24ff
Compare
kirkbrauer
marked this pull request as ready for review
November 19, 2026 14:41
Sessions and leases: - A suite that declares a session name for another exporter no longer keeps driving the one an earlier suite opened: the open session is closed and reopens from the new declaration. Declarations are re-asserted at start_suite, since Robot Framework reuses a library instance for a later suite with the same import. - Attaching to a named lease (lease_name or JMP_LEASE) no longer passes the selector, which made the client create a second lease when the two differed as text and then never release it. - Lease reuse skips leases that have not started, so a scheduled lease no longer makes a run wait for the acquisition timeout. - A bare Jumpstarter import attaches to JMP_LEASE, as documented. - Switch Session returns the session that was in effect, not `default`. - Call Driver, Get Driver, List Drivers and Use Device check the lease, so on_lease_end applies to them. Keywords: - Generators behind a functools.wraps decorator (validate_call on OpendalClient.list and scan) are keywords again rather than context managers; only contextlib makes one. - Static client methods keep their first argument. - Connect To Device converts its free options to the opener's types, so wait_for_boot=False is false. - A mistyped scope is rejected before anything is opened; it used to leave the SSH connection, the forward and the device's private key file behind, and the same for ADB and iOS. - List Drivers escapes exporter descriptions in its HTML table. Generation: - `generate --check` and `--capture` keep the children of a driver whose client package is not installed. - `--output` and `--session` are refused for several clients instead of writing every resource to one file. Require Robot Framework 7.5: before it a test timeout was an Exception, which the wait loops here catch, so a [Timeout] could be swallowed. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018WEcV3Ry2JEJgNrEy9cUQR
This branch has not been deployed
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
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.
Summary
Native Robot Framework support for Jumpstarter, in a new
jumpstarter-robotpackage. Every driver's client methods become Robot Framework keywords without any driver changes. Robot Framework runs get leases the same ways the Python helper does, and the integration builds on the shared Appium interface from #1283, which this PR is stacked on.What's included
Keywords for every driver:
jumpstarter_robot.Driverlibrary whose keywords come from its client class, statically. RobotCode and libdoc see them with arguments, types and docs, with no lease.dut.powergivesDut Power On). Aliases inrobot.tomlrename a prefix.Call Driver,List DriversandList Driver Keywordsreach and list everything.Client resources:
jmp robot generate(alsojmp-robot, orpython -m jumpstarter_robot) writesclient.resourcefromrobot.toml[tool.jumpstarter.client].nodesmapping (for users without the exporter config), a live lease, ajmp describedump, or an ExporterClass.--captureand--checkkeep the committed mapping in sync. Insidejmp shell,--captureworks out the client from the shell's lease and labels.jmpadds therobotgroup only whenjumpstarter-robotis installed, the same way it addsjmp mcp. The package's exports are lazy, so this costsjmpabout 1 ms at startup and doesn't load Robot Framework.Leases, for parity with
JumpstarterTest. There are three ways:JMP_LEASE, or automatically the client's active lease with the same selector (the IDE case).jmp shell.Acquire Lease.A selector alone never acquires a lease. Local mode serves an exporter config in-process. Named sessions support several exporters per run, and testbeds are YAML variable files.
Keyword sets:
Start Appium(orStart Device Hub Appium) returns the URL and capabilities for AppiumLibrary's ownOpen Application;Upload Apptokens go inappium:app. The same tests run on the iOS simulator and on a Device Hub iPhone (driver side in feat: add a shared Appium interface for iOS and Android UI automation #1283)Open Port Forwardfor existing Robot Framework remote librariesDriver-author API:
jumpstarter.client.decorators.robot(keyword,not_keyword,library) mirrorsrobot.api.decowithout depending on Robot Framework.jumpstarter.client.decorators.cli, and the old imports keep working.PowerClientgainsShould Be OnandShould Be Off.Core fixes:
resolve_root_childadded.reset.Works with: RobotCode's REPL (lease, discover keywords, drive the board) and pabot (one session per process).
Examples and docs
python/examples/robothas one folder per example. They run in local mode with plainrobotor RobotCode, anduv run pytest examples/robotchecks them all:basic/multi-dut/Use Devicelab/Acquire Leasezero-config/remote-library/linux-ssh/mobile/Docs: a Getting Started guide (
getting-started/guides/robot-framework.md) and a reference section (reference/package-apis/robot/) covering client resources, sessions and leases, devices and apps, and the full keyword reference. The Appium guide links to it.Testing
jumpstarter-robottests,examples/robottestsjumpstartertestsjumpstarter-clitestsThe example tests include:
analyzeper example folder: every keyword resolves.jmp robot generatewrites.Verified live earlier on this branch (before the latest naming and lease changes):
Not verified:
🤖 Generated with Claude Code