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.
Define the configuration of your browser test.
<KEY>:<VALUE>format to filter on a
<VALUE>for a given
<KEY>on the Synthetics page.
An alert is triggered if any assertion fails for
<INSERT_NUMBER> minutes from any
To configure your notifications:
Use the actions available in the upper left corner to enrich your scenario:
Note: Your last browser test step must be an Assertion, otherwise there is nothing to check.
Once you have finished your Scenario, click on Save and Launch Test.
Assertions allow you to check if an element, a content, or some text is available in the current page:
||Asserts that an element (such as a specific
||Makes sure that a specific element is located or not on the current page.|
||Asserts that some specific text is present on the current page.|
||Asserts that some specific text is NOT present on the current page.|
||This takes the URL of the last page that was interacted with, then asserts whether a specific value (
The navigation action allow you to:
This browser test step isn’t added through an actual hovering mechanism (otherwise each element you are hovering would be added as a step) but using a dedicated action with a click.
After selecting the Hover action, click on the element you want to choose to create a new step.
To create a variable, first give it a name then define its value from:
div, etc. content by extracting the text of this element.
||Generates a numeric string with n digits.|
||Generates an alphabetic string with n letters.|
||Generates an alphanumeric string with n characters.|
Once created, use your variable to set an input text on a form or search bar. Use the little hand on your variable box to create an input step:
You can also use your variables in some assertions, including:
To use your variables in one of your assertions, hit Use Variable and select the variable you want to use:
A test is considered
FAILED if it does not satisfy its assertions or if the request failed for another reason. You can view specific browser test errors by clicking on the error in the step results.
Common failure reasons include:
||The connection was abruptly closed by the remote server. Possible causes include the webserver encountering an error or crashing while responding, loss of connectivity of the webserver, etc.|
||The DNS entry is not found for the check URL. Possible causes include misconfigured check URL, wrong configuration of your DNS entries, etc.|
||The configuration of the check is invalid.|
||The SSL connection couldn’t be performed.|
||The request couldn’t be completed in a reasonable time. Browser tests timeout in 60 seconds. To override a timeout, change the time (in seconds) in the Assert that an element is present on the page step.|