What you can test

Klarent covers what mobile tests need, not just tapping through screens. Describe the scenario in plain English and Klarent sets it up on the device. For example:

• File system: pick and upload files with the file picker
• Camera: open the camera flows of your app
• Network: go offline, use airplane mode and other connection changes
• Device settings and time: change the device time, jump forward or back in time and check how the app reacts
• Gestures and permission prompts: swipes, pull-to-refresh, allow or deny dialogs

This also makes it possible to check exploits and edge cases, like time jumps and device time changes, that are hard to cover by hand.

This list is only a subset. We can do this and much more, so describe the scenario you need and Klarent will work out how to set it up.

On iOS, file picker flows need an extra Simulator build, see App builds.

Example: airplane mode

To test how the app behaves offline, add an instruction like Set the device to operate in airplane mode. Klarent adds an Enable airplane mode step and generates the code for it.

Look at the top bar of the device. Before the step (top), the Wi-Fi and connection icons are shown. After it (bottom), they are gone and the app shows its offline message.

Example: camera

Flows that open the camera work too. Here the test taps the capture button, accepts the camera information screen and verifies that the camera screen is opened, with its title and preview.

Example: file system

To test a file upload, describe the flow in the instructions. Here the test opens the file picker of the device, selects the Downloads category and picks a PDF.