What is Studio?

Studio in one sentence

Orbittest Studio is a Windows desktop workspace for Android QA. It combines device mirroring, UI inspection, logcat, editing, test running, and evidence reports in one local tool.

Why it exists

Mobile QA often requires moving between a terminal, device screen, logcat, editor, file explorer, and report folder. Studio brings those surfaces together so the tester can focus on the workflow instead of tool switching.

How it relates to OrbitTest

Studio uses OrbitTest mobile APIs for automation and adds a visual desktop layer for authoring, running, and diagnosing tests on connected Android devices.

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.