Creating mobile tests
Creating a mobile test works like creating a web test. The difference is that you select an app build instead of entering a website URL. The AI agent then launches your app on a cloud-hosted device and follows your instructions.
Watch the video: Autonomous mobile app testing on Android and iOS →Creating a mobile test
Section titled “Creating a mobile test”- Click
Create a testin theTeststab. - Switch the toggle from Website to Mobile App.
- Enter a Test case name.
- Open Select mobile app and choose your build, or choose Upload new mobile app. See App builds.
- Write your test instructions in plain English in Describe what to test.
- Click
Create test, orSave as Draftto generate it later.
The steps are the same for iOS. Just select an .ipa build in Select mobile app instead of an .apk.
Basic fields
Section titled “Basic fields”| Field | Value |
|---|---|
| Test case name | any string |
| Mobile app | the Android or iOS build to test |
| Describe what to test | what the test case should do and verify |
Options
Section titled “Options”Use the + button below the instructions, or type @, to add:
| Option | Value |
|---|---|
| Variables | Local variables, used only in this test case |
| Secrets | Project-wide secrets, like usernames and passwords |
| Modules | Reusable steps to run before the test, see Modules |
Browser states are for website tests only.
Settings
Section titled “Settings”Click Settings at the top right of the dialog for advanced options.
| Setting | Value |
|---|---|
| Locale | The locale (language and region) the app runs with during the test |
| Disable network capture | Turn on to stop network activity from being recorded for the run |
Writing instructions for mobile
Section titled “Writing instructions for mobile”The best practices for web tests apply here too. A few more tips for mobile:
- Name things the way they appear on screen, e.g.
Tap Sign Up and fill in the ID number field. - Say how to handle system prompts, e.g.
Allow notifications if prompted. - Describe gestures explicitly, e.g.
Perform a pull-to-refresh on the homepageorSwipe left on the first card. - Device-level setup works too, e.g.
Set the device to operate in airplane mode. - Say what should NOT happen, e.g.
Do NOT tap Confirm payment. - Use secrets for credentials, e.g.
@usernameand@password.
More ways to create tests
Section titled “More ways to create tests”Use From existing tests to let the Explore agent suggest related scenarios from a mobile test you already have. See More ways to create tests.