Browser tests are scenarios executed by Datadog on your web applications. They run at configurable periodic intervals from multiple locations around the world, and from multiple devices. These checks verify both that your applications are up and responding to requests, and that any conditions defined in your scenarios are met.
In this example, a browser test is configured to map a user’s journey from adding an item to cart to successful checkout. If any step during the browser test fails, it throws an error that is recorded in Datadog as a Test Result.
Define the configuration of your browser test:
https://www.shopist.ioas a test web application.
shopiston your test. Tags will help to keep things organized and allow you to quickly find the tests you’re interested in on the homepage.
Set alert conditions to determine the circumstances under which you want a test to send a notification alert.
To avoid being alerted on network blips that might happen on specific locations, this test is configured as:
An alert is triggered if your test fails for 0 minutes from any 3 of 13 locations
To ensure that a test execution is only considered a failure after two failed test runs, specify how many times you want your test to be re-run before being considered a failure:
Retry 1 time before location is marked as failed
Note: By default, there is a 300ms wait before retrying a test that failed. This interval can be configured via the API.
Write an alert message and specify which email addresses should be notified when the alert is triggered. No additional set up is required to start receiving alert emails from Datadog. You can also use integrations, such as Slack, PagerDuty, webhooks, etc., to receive alert notifications.
Click Save & Edit Recording.
Once this extension is installed, begin recording your test steps by clicking the Start Recording button. Navigate your page in the iframe to the right of the recording options. When you select a div, image, or any area of your page, the steps are recorded and used to create steps within the browser test. Learn more about each step in the browser test steps doc.
For example, to record test steps that map a user’s journey from adding an item to cart to successful checkout:
Note: the website used in this example regularly throws an error causing it to intentionally fail. If you set your email address in the message box, you should consequently receive a notification email when the test failure occurs.
A browser test homepage will automatically populate after save. This page includes property information, historical graphs for response time and uptime, sample results, and all events and test results. Test results include screenshots, errors, resources, and traces for each step.
Wait for your test to generate several test results or hit
Run test now to trigger them more quickly. Then look for a failed test result under Test Results or in your mailbox. The failed test step in is highlighted with a red
x. Click the failed step to begin troubleshooting.
https://api.shopist.io/checkout.json, posted the status ,and the targeted source of the problem is a controller linked to checkout. You have now successfully found the route of the problem.
The Traces tab is accessible with Datadog APM integration with Synthetic Monitoring. Once configured, it allows you to go from a test run that failed to the root cause of the issue by looking at the trace generated by that test run. To link browser test results with APM, whitelist the URLs you want the APM integration headers added to. Use
* for wildcards:
After you set up your first browser test: