Test results and performance data are accessed from the Step Results section when clicking on a specific test result. You can also use Sample Results as a way to quickly look into the latest failed test runs and compare them with recent successful ones.
A test 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 backend traces generated by their steps.
Common browser test errors include:
Element located but it's invisible
Cannot locate element
Select did not have option
General test failure
Each step where a full URL is loaded contains page performance information.
Google’s Core Web Vitals are a set of three metrics designed to monitor a site’s user experience. These metrics focus on giving you a view of load performance, interactivity, and visual stability. Each metric comes with guidance on the range of values that translate to a good user experience.
First Input Delay is available when using Real User Monitoring where real user or field data is available.
Learn more about Real User Monitoring and Core Web Vitals.
The Errors panel shows the error, its type (
network), and status (network status code).
The type of error is logged during interaction with the page. It corresponds to the errors collected between the time the page is opened and the time interaction with that page is realized.
The maximum number of errors that can be displayed is 8, for example 2
network + 6
A resource corresponds to the combination of requests and assets. The Resources panel shows:
The maximum number of resources that can be displayed is 50. Resources are ordered by the time when they start and then are displayed in Datadog by the first 50.
Resources can be filtered by resource type. Also, a search can be performed over the displayed URLs.
The traces panel shows your traces associated with the browser synthetic test. The UI is similar to the APM Trace View except for the following difference.
One browser step can make multiple requests to different URLs/endpoints, which results in several associated traces (depending on your tracing setup and on the URLs you allowed in your Settings). Use the dropdown to choose the trace to view.
Additional helpful documentation, links, and articles: