Skip to content
Luotsi Luotsi

Scenario-Based Android Automation

If you are looking for scenario-based Android automation, Luotsi fits when the flow is stable enough to move out of exploratory inspection and into JSON playbooks that engineers, CI, and shared labs can run the same way.

What scenario mode gives you

Section titled “What scenario mode gives you”
  • JSON playbooks with validated steps and metadata.
  • The same command surface locally and in CI.
  • Report outputs such as JSON, JUnit, and replay artifacts.
  • A clear handoff from live exploration into repeatable automation.
Section titled “Recommended starting path”
Terminal window
luotsi scenario-validate --path scenarios
luotsi run --path scenarios --device <serial>
luotsi replay packet --artifacts ./artifacts/<run>
luotsi replay packet --artifacts ./artifacts/<run> --check

Use inspect first when the flow is still changing. Use scenarios when the next goal is repeatability. After a run, start with replay packet and replay packet --check to get the At a Glance summary, failure snapshot, primary failure, recommended next action, and first-minute commands before choosing a deeper replay tool. Use replay open --dry-run when a human also needs the replay front door response.

Strong fit when

Section titled “Strong fit when”
  • The workflow needs to run in both developer and CI contexts.
  • You want the scenario definition to stay small and explicit.
  • You care about artifact capture and replay as part of the automation contract.

Weaker fit when

Section titled “Weaker fit when”
  • The flow is still too exploratory and changes every session.
  • You need a recorder-style visual authoring tool instead of JSON playbooks.

Open these next

Section titled “Open these next”