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 tests verify both that your applications are up and responding to requests, and that any conditions defined in your scenarios are met.
Define the configuration of your browser test.
Starting URL: The URL from which your browser test starts the scenario.
<COOKIE_NAME1>=<COOKIE_VALUE1>; <COOKIE_NAME2>=<COOKIE_VALUE2>.Name: The name of your browser test.
Select your tags: The tags attached to your browser test. Use the <KEY>:<VALUE> format to filter on a <VALUE> for a given <KEY> on the Synthetics page.
Devices: The devices to run your test on. Available devices are Laptop Large, Tablet, and Mobile Small.
Locations: The Datadog managed locations to run the test from. Many AWS locations from around the world are available. You can also set up a Private Location to run a Synthetics Browser test on a private URL not accessible from the public internet.
How often should Datadog run the test? Intervals are available between every 5 minutes to once per week.
You can use the global variables defined in the settings in the URL as well as in the Advanced Options of your browser tests. To display your list of variables, type {{ in your desired field.
You can customize alert conditions to define the circumstances under which you want a test to send a notification alert.
<INSERT_NUMBER> minutes from any <INSERT_NUMBER> of <NUMBER_OF_CHOSEN> locations. This alerting rule allows you to specify for how much time and on how many locations a test needs to fail before triggering the notification using.<INSERT_NUMBER> times before location is marked as failed. This allows you to define how many consecutive test failures need to happen for a location to be considered as failed. By default, there is a 300ms wait before retrying a test that failed. This interval can be configured via the API.A notification is sent according to the set of alerting conditions. To configure your notifications:
Enter a message for the browser test. This field allows standard Markdown formatting and supports the following conditional variables:
| Conditional Variable | Description |
|---|---|
{{#is_alert}} | Show when monitor alerts |
{{^is_alert}} | Show unless monitor alerts |
{{#is_recovery}} | Show when monitor recovers from either ALERT |
{{^is_recovery}} | Show unless monitor recovers from either ALERT |
Notification messages include the message defined in this section and information about the failing locations.
Choose your services and/or team members to notify.
Specify a renotification frequency. To prevent renotification on failing tests, leave the option as Never renotify if the monitor has not been resolved.
Click Save Details and Record Test.
Record your test.
Tests can be only recorded from Google Chrome. To record your test, download the Datadog Record Test extension for Google Chrome.
Use the steps available in the upper left corner to enrich your scenario:
Note: Your last browser test step must be an assertion to confirm the journey executed by the browser test resulted in the expected state.
Once you have finished your scenario, click on Save and Launch Test.
After saving a browser test, you can record steps which you can then edit or build on.
Steps are a series of actions that you can record for a browser test which you can then edit or build on. You can define the steps you want your browser test to go through either by directly recording them with the Datadog test recorder extension or by manually adding the step of interest. You can also configure certain steps with advanced options.
On this Page
