When we released Runtime Recovery Refresh earlier this month, it applied to every cloud run in an account that had it turned on. Now each plan chooses its own mode, so you can try a page reload on a few plans before you rely on it elsewhere. You can also now filter test output for reloaded steps and review step-level artifacts before and after mabl reloaded the page.
Availability
Runtime Recovery Refresh is rolling out to a small number of accounts at a time, and the mabl team enables it per account. If you would like it turned on for your account, reach out to your customer success manager.
Pick a mode per plan
The Runtime Recovery Refresh setting lives in the Advanced section of the plan edit form, alongside the retry settings, and offers three modes:
- On reloads the page and retries a failed step. A retry that passes lets the test carry on and finish as passed.
- Refresh, but fail the test at the end reloads the page and retries the step, and the test still ends as failed. Use it to see the rest of a run's failures while you're deciding whether to trust the reload.
- Off reports the failure right away, without reloading.
Plans start with the mode off, so nothing changes until you pick one and save the plan.
If your account already had Runtime Recovery Refresh
The account-level setting no longer turns reloads on by itself. Plans that were reloading and retrying before this change now run with the mode off until you set a mode on each one. Update Runtime Recovery Refresh in plan settings to On to keep it running.
Find and review reloaded steps
Two additions to browser test output make a reloaded step easier to read:
- A step filter. Filter the step list by Runtime Recovery Refresh to pull up every step mabl reloaded, whether or not the retry passed.
- An attempt switch. On a reloaded step, the Screenshots, Network, and DOM tabs each carry an Attempt switch. Initial attempt shows what mabl captured when the step first failed, and After refresh shows the reloaded page. Comparing the two is the quickest way to see what the reload changed.
A step whose retry passed still shows a badge under its status. Under Refresh, but fail the test at the end, the badge also explains why the run failed even though the step passed.