Actions are a series of steps that you can record for a browser test, which you can then edit or build on. You can also configure certain actions with advanced options.
Note: The default timeout for each step is approximately 60 seconds. You can override the timeout with advanced options.
Assertions allow you to check whether an element, some content, or some text is available on the current page. You can also check whether a specific email was sent.
|Asserts that an element (such as a specific |
|Selects an element and checks if it contains a specific value. For instance, you could select a |
|Asserts that some specific text is present on the current page.|
|Asserts that some specific text is NOT present on the current page.|
|Takes the URL of the last page that was interacted with, then asserts whether a specific value (|
|Asserts that an email was sent and whether specific values (|
Advanced options are also available for assertions.
The navigation action allows 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.
You can record the uploading of files as an action. To record an upload step you can:
This is limited to 10 files, with a limit of 5MB each.
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:
By default, Datadog waits for a page to be fully loaded before performing an action or a next step—with a timeout after 60 seconds. In some cases, however, you may wish to set a custom waiting time. For instance, if you know that a page or a page element is taking more than 60 seconds to load, you can leverage the wait step in order to extend that default timeout. If you choose to use this functionality, the value for your wait step must not exceed 300 seconds.
Note: This additional time is systematically added to each run of your browser test scenario.
You can run browser tests within other browser tests. Advanced options also allow you to choose where you want your subtest to be played.
Note: If it does not make sense for you to run your subtest independently, you can pause it. It will continue to be called as part of your main test, but it will not be executed individually.
Additional helpful documentation, links, and articles: