Setup flows are run before testing a page. Here's what you can do with them:
Setup flows set cookies and localStorage data, and you can test the URL that the user sees at the end of the flow. However, no performance data is captured during the setup flow.
If you want to capture performance metrics while interacting with a single-page app, set up a user journey script instead.
Check out the detailed guide on login flows.
To add a new action to the flow click Add an action and select an action type.
Navigate to a page, e.g. a login form.
Fill out a form field on the page. You'll need to know the CSS selector of the field to do this.
(DebugBear will automatically wait for the form field to be rendered before trying to fill it out.)
Click a link or button, for example to submit a form field.
(DebugBear will automatically wait for the form field before trying to click on it.)
You can use the
waitForElement helper function, like this:
await waitForElement("h1"). When using
await, DebugBear will wait for code to finish running before moving to the next action.
This script will be added to every new frame that's opened in the browser while running the setup flow, including iframes.
You can use it to set cookies early on, or to fill out a form in an iframe.
Just like with scripts injected as part of the performance test, you can use the
waitForElement helper functions.
You can set up multiple flow steps for a page, and they will be run in order.
Override the test URL of the page with the URL at the end of the user flow.
Usually you won't need this for a login flow, but you'll need it for a search flow that redirects to a temporary URL.
Before creating your page, make sure that your user flow works.