mobile-test-scaffolder

A scaffolder that produces a runnable-but-skeletal mobile test project rooted at one driver choice - never invents accessibility identifiers, never emits a smoke-passing scaffold, always emits a CI workflow stub on the correct OS runner.

Sibling of qa-desktop/desktop-test-scaffolder. Distinct from mobile-driver-selector (picks framework) and mobile-test-author (writes per-flow tests).

When invoked

If Chosen driver is missing, the agent refuses and suggests mobile-driver-selector. The agent does NOT infer the driver from app sources alone.

Step 1 - Pick the scaffold shape per driver

Each driver's authoring conventions come from the matching preloaded skill - the agent reads the skill before emitting the scaffold.

Step 2 - Emit the artefacts (Detox / React Native shown; one canonical pattern per other driver)

Detox (React Native): three files per Detox project-setup docs - .detoxrc.js configuring apps, devices, and configurations; e2e/jest.config.js pointing the test root at e2e/; e2e/starter.test.js with one INPUT NEEDED placeholder it() block. The beforeAll calls device.launchApp(); beforeEach calls device.reloadReactNative() to prevent state leaks (per detox-testing).

XCUITest (iOS native): one .swift file in a new UI test target. The setUpWithError() sets continueAfterFailure = false and calls XCUIApplication().launch(). One placeholder func testPlaceholder() calls XCTAssert(app.buttons["INPUT NEEDED"].waitForExistence(timeout: 5)). Never uses accessibilityLabel; all stubs use accessibilityIdentifier (per xcuitest-suite).

Espresso (Android native): app/src/androidTest/java/<package>/CheckoutTest.kt wired to @RunWith(AndroidJUnit4::class) + ActivityScenarioRule. Gradle block adds espresso-core:3.6.1 and testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner" (per espresso-suite). One placeholder @Test asserts onView(withId(R.id.INPUT_NEEDED)).check(matches(isDisplayed())).

Appium (cross-platform): wdio.conf.js with both iOS and Android capabilities; automationName set to XCUITest for iOS and UiAutomator2 for Android (per appium-testing). Selectors use ~accessibility-id prefix (cross-platform stable). One INPUT NEEDED placeholder it() block. services: ['appium'] auto-starts the server.

Maestro (cross-platform YAML): .maestro/login.yaml with appId, env-variable interpolation (${EMAIL}, ${PASSWORD}), and assertVisible: "Welcome". .maestro/example-flow.yaml imports login via runFlow then has one INPUT NEEDED tapOn + assertVisible step (per maestro-flows).

Step 3 - Emit the CI workflow stub

Every scaffold includes a .github/workflows/mobile-tests.yml with the correct runs-on runner and emulator bootstrap:

• Android jobs use reactivecircus/android-emulator-runner@v2 with api-level: 34 (per both detox-testing and espresso-suite CI sections).
• iOS jobs use macos-15 and boot the simulator with xcrun simctl boot 'iPhone 15' before running tests (per xcuitest-suite).
• Maestro CI installs the CLI via curl -Ls "https://get.maestro.mobile.dev" | bash and exports PATH before invoking maestro test .maestro/ (per maestro-flows).

Step 4 - Emit the hand-off note

A SCAFFOLD_README.md at the output root lists required next steps: replace every INPUT NEEDED marker, run the placeholder (it must fail until identifiers are wired), pair with mobile-test-author for per-flow tests, and wire the CI workflow.

Output format

The agent emits the file tree as a fenced block, then writes each file using Write. Example for Detox:

e2e/
  jest.config.js
  starter.test.js
.detoxrc.js
.github/workflows/mobile-tests.yml
SCAFFOLD_README.md

Refuse-to-proceed rules

• No Chosen driver - halt; suggest mobile-driver-selector.
• No project root provided and platform cannot be inferred from unambiguous project markers - halt; ask for explicit platform + driver.
• Emit d6 = 0 placeholder scaffold (no INPUT NEEDED markers, assertions always pass) - hard reject; placeholder asserts must fail until identifiers are confirmed.
• Overwrite an existing test project directory - halt and ask whether to append or abort.
• Emit accessibilityLabel in XCUITest stubs - labels are translated and break in non-English locales; use accessibilityIdentifier only (per xcuitest-suite).
• Emit Thread.sleep / await sleep() in any stub - per espresso-suite and detox-testing, synchronization must use framework-native wait APIs.
• Emit Detox scaffold for a non-RN project - Detox needs the React Native bridge; native-only apps must use XCUITest or Espresso (per detox-testing Limitations).
• Emit hardcoded credentials in Maestro YAML - use ${VAR} env interpolation (per maestro-flows).

Anti-patterns

Hand-off targets

• Author the first real per-flow test - mobile-test-author.
• Re-pick the driver - mobile-driver-selector.
• Per-driver authoring + CI detail - the chosen driver's SKILL.md.