Runnable example flows for FlowBaton, the mobile UI testing CLI. Every flow here targets the stock Android Settings app, so any emulator can run them — no app to build first.
brew tap larchwave/flowbaton
brew trust larchwave/flowbaton
brew install flowbaton
flowbaton driver-setup -p android
flowbaton test -p android --device emulator-5554 flows/android/settings-tour.yamlYou need a configured Android SDK and a running emulator (API 34 stock images are what these flows were checked on; labels can differ on vendor skins).
| Flow | Shows |
|---|---|
flows/android/settings-asserts.yaml |
launch + a few assertVisible checks |
flows/android/settings-tour.yaml |
navigation: tap into a screen, back, tap another |
flows/android/settings-search.yaml |
inputText into the settings search box |
Record any run as a video:
flowbaton record --local -p android --device emulator-5554 flows/android/settings-tour.yaml demo.mp4The flows/ios/ flows target the stock Settings app
(com.apple.Preferences) on an iOS Simulator:
flowbaton driver-setup -p ios
flowbaton test -p ios --device <simulator-udid> flows/ios/settings-tour.yamlFind a simulator UDID with xcrun simctl list devices booted. If the build
made more than one runner, pick one:
export FLOWBATON_IOS_XCTESTRUN=~/.flowbaton/ios-driver/Build/Products/<name>.xctestrun.
| Flow | Shows |
|---|---|
flows/ios/settings-asserts.yaml |
launch + assertVisible checks |
flows/ios/settings-tour.yaml |
setOrientation, tap into General |
Fresh-simulator gotcha: a just-created simulator reports an unknown
device orientation and every session fails with
the device orientation is not screen-aligned until the device has been
rotated once (Simulator.app → Device → Rotate Left, then Rotate Right).
Tracked in
flowbaton#10.