Reviewing mobile runs

Test run is available from the test details page (Recent runs) or from a collection (View run details). See Analyzing test runs.

Find all the info in the mobile test run details:

• start time and elapsed time
• the device the run used
• executed steps, with device screenshots and code
• error message
• Appium traces for advanced debugging

Appium traces

Playwright traces are for web tests only. For mobile runs, click View traces on a step to open the Appium traces.

They contain:

• a video of the run on the device
• Appium tab: the commands sent to the device, with status and duration. Filter by text, errors only or a time range, and use Download to save them
• Network tab: network requests made during the run
• Page Source tab: the structure of the app screen

For example, a pull-to-refresh gesture shows up as a performActions swipe command, followed by getPageSource and getScreenshot for the step verification.

Debugging a failed run

1. Open the failed step and compare its screenshot to what you expected. Look for unexpected dialogs or permission prompts.
2. Check the error message and the step code.
3. In the Appium traces, use Errors only to find the failing command and watch the video around that time.
4. Fix the test:
   • If the app changed, use Heal this test.
   • If the step instruction was unclear, edit it, see Fixing test cases.
   • If the generated code is wrong, add a Coder hint.