Mobile
Platform mobile headers, Appium launch, and command parity
Mobile scenarios use Platform: mobile with Driver: native (default on mobile). Declare device and app metadata in block headers — StrikeTest opens the app at session start.
Required headers
| Header | Purpose |
|---|---|
OS: | Android or iOS |
Device: | Emulator name, USB serial, or simulator name |
Package: | Android appPackage or iOS bundleId |
Activity: | Android launcher activity (required on Android; ignored on iOS) |
Platform: mobile
Driver: native
OS: Android
Device: emulator-5554
Package: com.example.app
Activity: .MainActivity
Group: Smoke
Scenario: Home screen
Then I should see "Welcome"App open vs in-app navigation
| Concern | How |
|---|---|
| App open | Package: (+ Activity: on Android) at session start |
| In-app navigate | navigate to "…" — activity name or deep link inside the running app |
| Screen assert | should be on "…" — activity / screen identity |
| Container scope | scope to "…" / scope to "page" — same grammar as web frames |
Do not use navigate to for the initial launch.
Command parity
Element labels (fill, click, should have, store from, …) use the same quoted-label grammar as web. Native Appium strategies resolve elements automatically.
Some web-only asserts (for example values … sum equal) return an unsupported error on Appium.
Appium must be reachable (default http://127.0.0.1:4723) or configured in your CI matrix.