Skip to content

test: fix debug launcher journeys so the emulator job compiles - #18

Merged
scrimshawlife-ctrl merged 1 commit into
mainfrom
fix/android-emulator-launchers
Oct 8, 2026
Merged

scrimshawlife-ctrl merged 1 commit into
mainfrom
fix/android-emulator-launchers

Conversation

@scrimshawlife-ctrl

Copy link
Copy Markdown
Owner

Summary

  • Pull requests run demo launchers (emulator): the debug Demo and Local journeys on an Android emulator. The contract job on main is unchanged.
  • onAllNodes is called on the Compose test rule. The pinned BOM does not export it as a top-level androidx.compose.ui.test function, so importing it failed compileDebugAndroidTestKotlin.
  • Sign-in uses the synthetic account demo@example.invalid / 123456. The email check matches the prefilled field, because the hint contains the same address.
  • These tests are in androidTestDebug. They are not in a release build.

Verification

Local AVD suas-test (Pixel 6, Android 16, arm64), JDK 25, against commit 0dd5f12:

  • :app:connectedDebugAndroidTest class DemoLauncherSignInTest: 1 test, BUILD SUCCESSFUL. No server.
  • Same task, class LocalLauncherSignInTest: 1 test, BUILD SUCCESSFUL, against npm run dev:demo on 127.0.0.1:3000 (emulator base http://10.0.2.2:3000).

Not in this change

  • SPEC-018 stays KEEP_BLOCKED. No merge, no deploy, no store id, no production host.
  • This branch is from current main (9fae299). It does not update the older emulator draft.

EOF

LauncherJourney called onAllNodes on the Compose test rule. Importing it
as a top-level ui-test finder does not resolve against the pinned BOM, which
is why compileDebugAndroidTestKotlin failed. The journeys live in
androidTestDebug, sign in as demo@example.invalid with code 123456, and run
on pull requests.
@scrimshawlife-ctrl
scrimshawlife-ctrl marked this pull request as ready for review October 8, 2026 06:49
@scrimshawlife-ctrl
scrimshawlife-ctrl merged commit 18ac773 into main Oct 8, 2026
2 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-08T06:57:22.543467Z 0dd5f12 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant