A Mobile Run has its own settings, separate from the browser settings a web Test Run uses. They control how the Mobile App starts, which way the device is held, what the app is allowed to access, and how the device reaches the network. You find them in the run settings panel of a Mobile Test Case, under Show advanced settings, and you can put everything back with Reset to defaults.
App reset
App reset decides what your Mobile App knows at the start of a Mobile Run. It is the setting that most often explains why a Test Case passes alone and fails in a Test Set.
Option | What happens |
No reset | Keep app data between runs |
Full reset | Wipe app data and reinstall |
Fresh install | Uninstall then reinstall from build |
Choose No reset when the Test Case depends on state an earlier Test Run left behind, such as an existing login. Choose Full reset or Fresh install when the Test Case must start from a clean install, for example when you are testing onboarding.
Orientation
Set Orientation to portrait or landscape for the Mobile Run. Use it when a screen only behaves the way you want to test in one of the two.
Run behavior
Run behavior covers appearance and highlighting during the Mobile Run. The setting here is Dark mode, which controls the system theme the device uses while your Test Case executes. Turn it on to test your Mobile App's dark theme without needing a separate device.
Connectivity
Connectivity controls the network and sensors available during the Mobile Run.
Wi-Fi
Cellular
GPS
Turn one off to test how your Mobile App behaves without it, for example what a screen shows when the device has no connection at all.
Permissions
Permissions decides what the Mobile App is allowed to access, so a system dialog does not interrupt your Test Case. Each of Location, Camera, Microphone, Photos and Notifications can be set to:
Allow, granted up front, and no dialog appears
Block, refused up front, which is how you test the refused path
Prompt, left to the system, so the dialog appears and your Test Case must handle it
Setting a permission to Allow is usually what you want, because it keeps a dialog you are not testing from stopping a Test Case about something else.
Device PIN and proxy
These cover the device unlock PIN and the proxy for the Mobile Run.
Device PIN is the passcode used to unlock the device. Some devices have a fixed passcode, and Thunders tells you which when they do.
Proxy host and Proxy port route the device's traffic through a proxy, which is how you reach an internal environment that is not on the public internet.
Frequently asked questions
How do I make a Test Case start from a known state?
Set App reset to Full reset, and the Mobile App is wiped and reinstalled before the run, so the Test Case begins the same way every time. No reset is the one to choose when you deliberately want to carry state over from an earlier run.
How do I grant the app its permissions up front?
Set each permission to Allow, and the Mobile App has it before the Mobile Run starts, so your Test Case goes straight to the screen it is testing. Use Prompt when the dialog itself is what you want to exercise.
How do I test what my Mobile App does with no network?
Turn off Wi-Fi and Cellular for the Mobile Run. Leave them on and turn off GPS instead if you want to test only the absence of location.
What is the difference between Full reset and Fresh install?
Full reset wipes the Mobile App's data and reinstalls it. Fresh install uninstalls the app first, then installs it again from the build. Use Fresh install when you need to be certain nothing from the previous install survives.
Where do I configure a web Test Run?
Web Test Runs have their own browser settings, separate from these.