Reference

Mobile Testing

Use Android automation through ADB and UIAutomator without an Appium server stack.

Page17 of 28

Reading timeCalculating

Sections0

Documentation goal: this page is written as practical product documentation, with enough context to help a real QA engineer decide how to use the feature in a maintainable test suite.

Android-first workflow

OrbitTest mobile testing is designed for Android QA teams that want ADB and UIAutomator without running an Appium server. This keeps the stack smaller for Android-only work.

Device requirements

Enable USB debugging, authorize the host computer, verify `adb devices`, and use a data-capable USB cable. Many connection problems are caused by charge-only cables or stale authorizations.

Evidence

Mobile failures need device context. Capture app version, Android version, device model, screen state, screenshots, recordings, and logcat around the failed step.

const { test, expect } = require('orbittest/mobile');

test('app opens', async (orbit) => {
  await orbit.wakeUp();
  await orbit.launchApp('com.example.app', 'com.example.app.MainActivity');
  await orbit.waitForText('Welcome', 10000);
  expect(await orbit.hasText('Welcome')).toBe(true);
});

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.

Was this page useful?

Your response is saved in this browser and helps shape the docs experience.