Installation

Windows installer

Download the latest Studio installer from the release page. Because the installer may not be Authenticode-signed yet, Windows SmartScreen may ask for confirmation. Verify the published hash before running.

Android preparation

Enable Developer Options, turn on USB debugging, connect the phone with a data cable, and approve the debugging prompt. If the prompt does not appear, revoke USB debugging authorizations and reconnect.

Companion app

Studio deploys the OrbitTest Companion app to the device. Companion bridges screen streaming and device session information over the local ADB connection.

Practical checklist

• Keep the workflow readable enough that a QA engineer, developer, or product teammate can understand the intent without opening application source code.
• Prefer user-visible names, stable configuration, and clear evidence over hidden assumptions or brittle implementation details.
• Run the smallest useful check locally before adding it to CI, then verify that failures produce screenshots, logs, traces, or reports that explain what happened.
• Review this part of the suite regularly so outdated examples, stale setup, and obsolete workarounds do not reduce trust in the automation.

Common mistakes to avoid

• Do not add automation only to increase test count. Each page and test should protect a clear user journey, release risk, or debugging need.
• Do not hide important behavior inside helpers so deeply that the test no longer explains what the user is doing.
• Do not rely on fixed sleeps when the application can expose a meaningful ready state such as visible text, URL change, element availability, or completed evidence capture.
• Do not ignore failing artifacts. A report, screenshot, trace, or log entry should feed back into better product code, better waits, or clearer test data setup.