The mabl Trainer

Getting started

When you open a browser test in the mabl Trainer, two windows appear:

• A Chrome browser window
• The mabl Trainer window

This guide outlines how to record and run steps in the mabl Trainer.

Default steps

When you start to record steps in a new browser test, two default steps are added to the beginning of the test:

• Set viewport size to width 1000 and height 800 (This step is ignored in mobile tests.)
• Visit URL assigned to variable "app.url"

The record button

When the record button is turned on, the mabl Trainer records your interactions with the application under test as test steps (recorded actions). If you want to take a break from recording steps in a training session, you can turn the record button off.

The Trainer cursor

The Trainer cursor (...Waiting for input) indicates where new steps are recorded.

📘

Moving the Trainer cursor

Learn more about the different ways you can move the Trainer cursor to another part of your test here.

Adding steps

Recorded actions

When the Record button is turned on, the Trainer will record your interactions with the browser window, including clicks, right clicks, text input, keypresses, page refreshes, and visiting a new URL.

📘

Note on right click steps

The mabl Trainer only records right clicks on applications that show a custom right-click menu, also known as a custom context menu. The Trainer cannot capture interactions with the default right-click menu in your browser window because it is not part of the DOM.

Variables

Click on the {x} icon to create, manage, and use variables in your test.

Assertions

Click on the checkmark icon to create assertions.

Add step menu

Click on the + icon to add a new step, including the following:

• Conditionals
• JavaScript steps
• Wait steps
• Accessibility checks
• Flows
• Custom find steps
• Visit URL steps
• Echo steps
• Mabl mailbox steps
• API steps
• Steps that set, assert, and remove cookies

Use the search bar to quickly find the step you're interested in. You can navigate the step menu using the "tab" key to select the next option and the "enter" or "space" key to confirm your choice.

Running steps

Running steps, also known as Trainer replay, serves many purposes, including:

1. Verifying that your test steps produce the expected result
2. Getting your application in the correct state to record new steps
3. Replaying a single step to observe its behavior while troubleshooting

Play from beginning

If you want to play back all test steps, take the following steps:

1. Move the Trainer cursor to the beginning of the test.
2. Click on the play icon.
3. Select Play from cursor.

Play through here

Play through here is a helpful option when you want to get your application in a specific state, either for troubleshooting or recording new steps.

1. Move the Trainer cursor to the beginning of the test.
2. Identify the test step you'd like to play through.
3. Click on the More actions (...) menu
4. Select Play through here.

Play step

Use the play step option to get quick feedback on a step or to observe the behavior of a step that is causing errors or failures:

1. Ensure that your application is in the correct state to execute the step.
2. Click on the More actions (...) menu
3. Select Play step.

Play from cursor

You can play back steps from wherever the Trainer cursor is located:

1. Click on the play icon.
2. Select Play from cursor.

📘

Note

If the Trainer cursor is at the end of the test, you will see an option to Play from beginning instead.

Pause Trainer replay

When the test is playing, the play button turns into a "pause" button, which you can use to pause Trainer replay:

1. Hover over the rotating arrows.
2. Click on the pause icon that appears.
   Clicking pause stops execution after finishing the currently running step.