For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/synthetics/mobile_app_testing/mobile_app_tests/results.md.
A documentation index is available at /llms.txt.
This product is not supported for your selected Datadog site. ().
Overview
Click on a mobile app test on the Synthetic Tests page to see the Test Details page. The Test Details page contains all the information relating to your test, including test activity, test results, performance metrics, and test properties.
Test runs appear in a test details page after a Synthetic mobile app test executes. Test results correlate to the latest passed and failed test executions over a time interval and in a specific number of locations and devices.
Test activity
On the Activity tab, you can see:
The Global Uptime graph, which displays the total uptime of all test locations in a given time interval. The global uptime visualization displays red only if the alert conditions configured for a test are triggered in the given time interval. Since location uptime is computed based on the final test result after retries complete, fast retry intervals directly impact what appears in your total uptime graph. For more information about uptime monitoring, see the Uptime Percentage widget guide.
A Timeline of alert triggers, recoveries, and test modifications.
A detail panel for the selected alert showing what happened, the failing result, and suggested next steps for investigation.
Test results
On the Test Results tab, you can examine the latest failed test runs and compare them to recent successful test runs. Mobile app test runs include components such as screenshots to help troubleshoot your test failure.
Test run columns
The following describes each column in the Test Results table:
The version of the mobile application used in your test run.
Test version
The version of the test that was executed.
Run type
The type of test run (CI, manually triggered, or scheduled).
Video replay
A recording of the test execution available for diagnosing failures. See Video replay.
Screenshots and actions
Every executed test step contains a screenshot of the step action, step action name, step ID, and step duration.
Screenshots can be disabled by checking “Do not capture screenshot for this step” in the Advanced Options section.
Video replay
Use video replay to diagnose test failures by showing unexpected UI behavior or pop-ups that may have caused the issue. Video replay requires screenshots to be enabled. Disabling screenshots for a step prevents video replay for all test runs.
Click the video icon ▶️ for a failed test run on the Mobile Application test details page to watch the complete test execution. You can also access video replay for all test runs using the Video Replay tab in the test run side panel, which provides detailed test run information.
Note: Mobile Application test session replays are not available in RUM.
XML highlighting
Results of steps contain the XML representation of the screen being tested, as well as the ability to hover over the screenshot or the XML to highlight specific elements of the app.
Click an element to view additional attributes:
Test performance
On the Performance tab, you can see aggregate performance metrics across all runs of your test:
Average Test duration by location, which displays the time the test takes to complete in each location.
Average Step duration, which displays the time each step takes to complete across runs.
Test properties
The Properties tab contains the configuration details, ownership information, and integrations associated with your test. Use the left navigation to switch between sections.
Properties tab sections
The following describes each section available on the Properties tab:
Ownership
Displays the test owner, editor, creation date, last modified date, environments, teams, and tags.
Execution
Shows the test frequency, alert conditions, and retry behavior.
Monitor
Contains the Synthetic test monitor name, priority, configured recipients, and notification message.
Click on a failed test to open the side panel and download the crash report in the Run Details tab:
Failed results
A test result is considered FAILED if it does not satisfy its assertions or if a step failed for another reason. You can troubleshoot failed runs by looking at their screenshots, checking for potential errors at the step level, and looking into resources generated by their steps.
Common mobile app test errors include:
Element located but it's invisible
The element is on the page but cannot be clicked on—for instance, if another element is overlaid on top of it.
Cannot locate element
The element cannot be found in the XML.
Test events
Alerts from your Synthetic test monitors appear on the timeline in the Activity tab, where you can review alert triggers, recoveries, and test modifications alongside the global uptime graph. To search for alerts from Synthetic tests in the Events Explorer, navigate to Events > Explorer and enter @evt.type:synthetics_alert in the search query. For more information, see Using Synthetic Test Monitors.
Further reading
Additional helpful documentation, links, and articles:
