Defining a journey with the mabl trainer

Journeys are part of the core of mabl's functionality. You define these journeys by using the mabl Trainer to record clicks, finds, JavaScript steps, variables, and much more. The steps below detail how to get started creating your first journey through the mabl trainer.

Defining a new Journey from the mabl app

  1. Simply find and click the "New Journey" button in the left-hand navigation.
  1. We'll walk you through the basics. Name your Journey, and give it descriptions or labels if you wish. Then, add it to a Plan (where you define properties about how often a journey runs and other dependencies). There will also be advanced options, such as adding login flows, data tables, and user-supplied credentials.
Basics of new journey setup

Basics of new journey setup

Advanced journey settings

Advanced journey settings

  1. A new tab will open with the "Ok, train me " dialogue box.

Please be sure to disable any auto-fill applications or extensions when training.

While mabl attempts to capture auto-fill actions, it is best to manually perform each step that you wish to include in the training.

mabl trainer in Chrome window

mabl trainer in Chrome window

  1. Use your application as you would like mabl to test it, be sure to click "Okay, train me!" to begin.
  2. To add an assertion, click the "Add Assertion" link in the trainer.
  3. To delete a step, hover over the step and click the "Delete" icon.
  4. You can replay specific steps with the small play icon in the upper toolbar of the trainer.
  5. When your Journey is complete, click "Save Journey". You will be taken back to the journey details page.
Example of a journey

Example of a journey

Hovers, flows, Javascript steps, cookie steps and more lie in the "..." icon, which opens up a secondary menu of actions.

Hovers, flows, Javascript steps, cookie steps and more lie in the "..." icon, which opens up a secondary menu of actions.

Defining a journey from the mabl extension

You can start training a journey from any page on Chrome in seconds, all without having to open the mabl app. Just follow the steps below to get started.

  1. Click the mabl extension in Chrome, located in the top right corner of the browser.
The location of the mabl extension.

The location of the mabl extension.

  1. Select the workspace you'd like to add the journey to. Be sure to select the correct one, as journeys cannot be shared between workspaces.
  2. Name the journey next. You can also give the journey a description, although this is optional and can always be added later.
  3. Click "Start training" to immediately start recording your new journey.
  1. A modal appears confirming that you've started training, just dismiss this as you normally would.
  2. Start recording your test! Follow the steps 6 through 9 in the above section for more information about training with the mabl trainer.

Important information about training from the extension

When using the above method to record journeys, be sure to add your journey to a plan to run the journey. Without being added to a plan, a journey cannot run.

Viewing the mabl trainer in Chrome DevTools

A larger mabl trainer can be viewed in the Chrome DevTools panel, allowing you to view more steps and more information about your journeys than the standard mabl trainer window. You also can resize the panel to suit your testing needs.

The mabl trainer expanded in DevTools.

The mabl trainer expanded in DevTools.

When opening the panel, be sure to hide the smaller mabl trainer so it doesn't get in the way.

Information about resizing the mabl trainer in DevTools

Resizing the mabl trainer while in DevTools will affect the viewport of your app when recording tests. Be sure that all elements are still in the correct place when resizing. You should make sure your app has not switched to a mobile format as well, as both may negatively affect testing.

Defining a journey with the mabl trainer


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.