API and browser scenarios
Check the whole user journey: sign-in, placing an order, payment, not just individual URLs.
The task
Each URL can respond on its own while the whole flow is broken: no token is issued, a created entity cannot be found, a button on the page does not work.
How it is solved
An API scenario consists of request steps. A value from a step’s response is extracted into a variable and substituted into the next request. A browser check opens the page in a real browser and runs the steps: go to, click, fill in, wait for an element, check text.
What is included
- An API scenario of three or more steps, each with its own conditions
- Extracting values from JSON, headers and text into variables
- Secret variables live only in the memory of the run
- Browser: go to, click, fill in, wait for element, check text
- The browser window size is set in the check
- The time and result of each step are shown separately
Limitations
- The number of scenario steps is limited by the plan.
- A browser check runs on a separate executor, so it has no test run button.
- Browser checks are not run by private agents.
Questions about this feature
How do I pass a token from a response to the next request?
Extract the value by JSONPath, from a header or from text into a variable, and reference it in the next step as {'{{'}name{'}}'}.
Does a browser check see text rendered by a script?
Yes. The check first looks for visible text on the page, then in the markup.
Where it helps
Other features
All featuresCheck your services today
The free plan includes checks, a status page and a team of up to three people. The setup wizard takes you from a product to the first notification.