If your test is failing because a step doesn't work as intended or runs into an issue, mabl lets you edit your test's steps while keeping only the important info: the URL, environment, application, etc.
You can edit your tests by launching the mabl trainer or within the app itself.
It only takes a few steps to edit your tests:
- Make sure you're on the tests page, and that you've trained at least one test in the past. Note: You cannot edit the two automated tests that mabl creates and runs for each app.
- Notice the checkbox next to each test. Click on the one(s) you would like to edit.
- Click on the "Edit steps" button at the top right of the screen.
- You have two choices: Quick Edit, which lets you edit the test in the app, and Launch Trainer. If you choose Launch Trainer, you will be directed to the beginning of the test. Simply continue as you normally would through the test. If you want to cancel any changes, simple click the "Cancel" button at the bottom of the trainer. Your changes will only be saved if you click the "Save" button.
Did you know?
You can open the mabl trainer in Chrome DevTools to more easily view your steps and important information for easier editing.
Selecting "Quick Edit" mode when editing a test pops the trainer into the mabl app itself, allowing you to edit most steps. You can edit almost everything, as long as it does not require interaction with the app under test. Because of this, creating new steps such as assertions and clicks, as well as replay, are not available in quick edit mode. Among the allowed features are: deleting steps, editing assertions, add waits, reordering steps, creating flows, and more.
You can save your edited tests as many times as you'd like, as long as you've altered, added, or removed at least one step since you opened the test. When you save, the trainer will display a confirmation message. You can continue training as normal after your save. Just click the "Close" button to return to the app.
The confirmation message after clicking save. Also, note that the "Save" button is grayed out as no changes have been made since the previous save.
Even if you accidentally click Close when you've edited your test, mabl will prompt you with a modal asking if you'd like to save. You can discard the changes since the last save and return to the app, save the new changes and return to the app, or cancel and return back to the trainer.
Important information about editing tests
mabl does not place limits on how many users can edit a test at one time. Thus, it's important to coordinate with your team members to be sure new changes aren't saved over by another user. If you believe this has taken place, please contact mabl support in-app or at [email protected] so we can resolve this issue for you.
Use caution when dragging and dropping steps to reorder them. Make sure you're on the correct page when recording steps. Adding steps to the test from the wrong page can cause the mabl trainer to fail.
You can easily step through parts of your trained tests using the arrow keys, as long as the trainer is "in focus." When the trainer is in focus, it will display "edit" in the upper righthand side of the trainer.
Simply press the arrow keys up or down to move the magenta status bar throughout the trainer test. Be careful about adding steps in the wrong place, since clicks, entered text, and similar will still be recorded while you're stepping through your tests as long as you are not in replay mode.
By using the arrow keys to step through your test, you can add steps just about anywhere. You must be aware of when and where you are adding steps, as adding steps to the test from the wrong page can cause mabl to fail later on. Always be sure to be on the correct page when recording new steps.
Since mabl allows you to replay each step of your test with the trainer, it is also used to step through which part of the test you would like to add your new step to.
Please see the gif below to understand how to properly edit and insert a step using replay.
Steps without edit support
There is currently one step that you cannot currently edit, due to limitations:
- Changing assertions on properties or Variables
Updated 3 months ago