Studio

Quick Start

Create a Studio project, connect a device, write a mobile smoke test, and review evidence.

Page22 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.

Create a project

Open Studio and create a new project or open an existing folder. Keep mobile tests in a clear directory such as `tests/mobile` so reports and source files are easy to find.

Run a smoke test

Start with one test that launches the app and verifies a visible home screen label. This confirms ADB, app launch, waits, and reporting before you automate deeper flows.

Review evidence

After the run, inspect stdout, final screenshot, action log, and device recording. This review step helps you catch environment issues early.

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

test('home screen opens', async (orbit) => {
  await orbit.launchApp('com.example.app', 'com.example.app.MainActivity');
  await orbit.waitForText('Home', 10000);
  expect(await orbit.hasText('Home')).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.