Editing tests

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.

How to edit your tests

It only takes a few steps to edit your tests:

  1. 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.
  2. Click on the name of the test that you would like to edit.
  1. Click on the "Edit steps" button at the top right of the screen.
  1. 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.

Disabling steps

When troubleshooting a test, sometimes it is helpful to just disable certain steps rather than deleting them. That way you can validate that everything else works well before deciding what to do with the disabled steps which are skipped over during test runs.

Disabling steps also helps you to continue running a test while a problematic area of the application is being worked on by your development team. For example, you can disable specific clicks and assertions on the page until a fix has been shipped. Then, after the application has been updated, you can simply re-enable the disabled steps to maintain the previous level of test coverage.

You can disable/enable a step from the corresponding more actions menu in the mabl Trainer. You can also do so in bulk by selecting multiple steps and using the bulk actions menu that appears at the bottom of the Trainer. Hold Shift and Click to select multiple steps at once.

More actions menu with an option to disable the step.More actions menu with an option to disable the step.

More actions menu with an option to disable the step.

Another use case for disabling steps is when you duplicate an existing test and are not sure which steps you want to keep or modify. In this case, you can disable most steps of the test while you work your way through the copied test. That way you can think of disabled steps as part of your to-do list of steps to review for that test.

Quick Edit: Editing your tests in the mabl app

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.

Saving your edited tests

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.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.

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.

Drag-and-drop editing

When you're using the trainer, you can drag-and-drop your steps to reorder them in any way you'd like. This is great if you don't want to have to step all the way through your test to add a simple wait step, Javascript step, or similar.

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.

Editing steps using arrow keys

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.

Editing steps with replay

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

Watch the next chapter in the quick start video guide.

Did this page help you?