Quick-edit mode

If you want to make updates to a browser test that don't involve interacting with the application under test or playing back steps, you can update the test in quick-edit mode instead of opening the full mabl Trainer.

Quick edit, as its name suggests, is a good option for making smaller changes to a test:

Updating a variable or assertion value
Adding a Configure Find attribute to a step
Disabling steps for troubleshooting purposes

What is supported in quick-edit mode?

Support for adding steps in quick-edit mode is limited to steps that don't require interacting with the application under test. The following table explains which steps can be created in quick-edit mode:

Type of step	Quick-edit support	Additional details
Recorded actions	No	Since there is no browser to interact with, recorded actions cannot be added in quick-edit mode.
Assertions	No	The assertion step is disabled in quick-edit mode. (Custom find assertions, created using a `Find element` step are still supported.)
Variables	Partial	You can create variables from all sources except Element property.
Flows	Yes	Quick-edit mode supports both creating and importing flows.
Conditionals	Partial	You can set conditions based on custom find, JavaScript, or a variable.
JavaScript	Yes	Quick-edit mode supports creating and importing snippets, but it does not support running snippets.
Wait	Yes
Wait until	No	Creating a `wait until` step requires interacting with the browser.
Accessibility	Partial	Accessibility checks that target the page are supported.
Custom find (`Find element`)	Yes	In the mabl Trainer, you can confirm whether the XPath or CSS for a custom find step matches an element on the page. In Quick Edit mode, since the app under test isn't open, this preview feature isn't available.
Visit URL	Yes
Echo	Yes
API steps	Yes
Cookies	Partial	Quick Edit supports creating and removing cookies; it does not support cookie assertions.
Set viewport	Yes