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
A test in quick-edit mode
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
|Since there is no browser to interact with, recorded actions cannot be added in quick-edit mode.
|The assertion step is disabled in quick-edit mode. Custom find assertions, created using a "Find element" step are still supported.
|You can create variables from all sources except Element property.
|Quick-edit mode supports both creating and importing flows.
|Quick-edit mode supports creating and importing snippets, but it does not support running snippets.
|Creating a "wait until" step requires interacting with the browser.
|Accessibility checks that target the page are supported.
|Custom find ("Find element")
|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.
|Quick Edit supports creating and removing cookies; it does not support cookie assertions.