Adding hovers

The mabl Trainer supports the ability to track user behavior for menu items that have hovers built into an application. With the following steps, you can easily add hovers into your journeys that might involve such interactions.

Adding hovers to a journey

  1. Make sure that the mabl Trainer is open in your window.
  2. Check the option "Record hovers", which is located in the "More actions" menu.
  1. Once the “Record” button is checked, click on the element of your application that you want to hover on, so the trainer can record it in your journey.
  2. Click all of the other elements you'd like to record in this hover step.
  3. When you are finished, you can uncheck the record hovers option.
  4. Continue training the remaining steps of your journey.
  5. If you would like to record any more hovers in your journey, repeat steps 2 - 5 above.
  6. Now, the trainer has saved the steps involving a hover that are recorded in your application.

Best Practices

Initially, some of the ways in which you can incorporate hovers into your journeys might include the following:

  • Activating drop-down menus
  • Displaying "add to basket" options on mouseover, particularly in e-commerce sites
  • Scrolling through various product views
  • Displaying the price of a product via a hover trigger
  • Displaying different views or colors of a product/image
  • Zooming into or out of product images
  • Providing additional information quickly for users in forms
  • Displaying side links or tooltips

Deleting Hovers

In order to delete the steps recorded in a Hover entry, you can simply hover over the steps you wish to delete, and a small "Delete" icon will appear to the right of each step. Clicking on this will delete the step, and you can continue through until all the steps related to a particular instance of a hover are fully deleted.

Watch the next chapter in the quick start video guide.

Adding hovers


Suggested Edits are limited on API Reference Pages

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