Cross Platform Gui E2E Test

Ropy Cross-Platform GUI E2E Test

Validate the packaged desktop application on every supported operating system. Complement GPUI in-process tests with real process, clipboard, global-hotkey, tray, focus, and window interactions.

Enforce the Platform Contract

• Inspect the host or guest architecture before selecting an artifact. Never use emulation silently.
• Run macOS on the local Mac. Do not spend AgentBay resources for macOS unless the user explicitly changes this policy.
• Run every Windows and Linux GUI test in a fresh virtual desktop. Do not substitute a local container, headless shell, WSL, or compile-only CI job.
• Require X11 connectivity for Linux. Ropy's Linux GUI integration is X11-specific; a DISPLAY variable without a reachable X server is insufficient.
• Report a cross-platform pass only when every requested platform row passes. Preserve separate results for each OS and architecture.

Read only the reference for the platform being exercised:

• macOS local run
• Windows AgentBay run
• Linux AgentBay run

Apply Shared Guardrails

• Resolve the release tag or commit requested by the user. Otherwise use the latest published release.
• Download artifacts to a temporary controller directory, inspect their contents, calculate SHA-256, and compare any publisher-provided digest before execution.
• Keep AgentBay credentials in an environment variable, secret store, or user-level MCP configuration. Never commit, print, or include a credential-bearing URL in output.
• Confirm paid-session authorization unless the current request already authorizes the virtual test. Do not enable postpaid billing, buy credits, or raise limits without separate authorization.
• Before creating a virtual session, inspect active sessions and billing controls. Prefer concurrency 1, a maximum runtime of no more than 30 minutes, and an idle timeout of at least 10 minutes.
• Create only one virtual session at a time. Record its identifier immediately and release it in a finally path. Explicitly terminate it; do not leave it running or hibernating.
• Use a unique marker such as ropy-e2e-<platform>-<uuid> so stale clipboard contents cannot create a false pass.
• Never record unrelated local clipboard contents, credentials, signed URLs, or user data in screenshots and logs.

Prefer Stable Virtual Control

For Windows and Linux, prefer these AgentBay paths in order:

1. Use a configured MCP endpoint with command, filesystem, screenshot, keyboard, and window capabilities.
2. Use the official AgentBay SDK with AGENTBAY_API_KEY supplied through the environment.
3. Use an AgentBay console debug session through the in-app browser only as a manual fallback.

Discover current tool names rather than assuming one SDK version. Prefer filesystem write_large_file or an AgentBay Context for artifact transfer. Avoid downloading release assets inside the guest: slow downloads may trigger idle-session reclamation.

If no supported control path is available, stop before creating a paid session and report the missing capability. Never place the secret endpoint in the repository as a workaround.

Run the Shared GUI Scenario

Use platform-native UI automation, screenshots, and window inspection at every assertion boundary:

1. Launch the verified packaged executable and assert that its process remains alive after three seconds.
2. Expect no initial visible window: Ropy intentionally starts hidden in the system tray.
3. Send Control+Shift+D, the default activation hotkey on all supported platforms, and assert that the Ropy window becomes visible.
4. Open a platform-native plain-text editor, enter the unique marker, select it, and copy it.
5. Wait briefly for clipboard ingestion, reactivate Ropy, and assert that the exact marker appears in history.
6. Press /, search for a unique substring, and assert that the matching record remains visible.
7. Select the record and press Enter. The default confirm mode copies the record back to the clipboard.
8. Return to the editor, paste, and assert that the pasted text exactly equals the marker.

Prefer semantic window, text, and accessibility queries. Use coordinates only after taking a fresh screenshot. Retry a flaky clipboard ingestion once with a new marker; collect state before retrying.