Echo steps

Adding echo steps to browser tests

Echo steps let you print logs to test run output. Echo steps can be useful in the following circumstances:

  • Describing the intent behind steps and flows for other members of your team
  • Visually breaking up the test into different parts to make the test easier to edit and review
  • Printing variable values to output logs to debug tests

Adding echo steps

In the mabl Trainer or quick-edit mode, move the cursor to the point in the test where you'd like to add an echo step. Then take the following steps:

  • Click the plus icon (+) to add a step.
  • Select Echo step.
  • Enter a message.
  • Click OK to add the echo step to the test.

When the test runs in the cloud, the message is printed in the Test Output page.

Echo steps as headers

If you put "#", “##”, or “###” at the start of an echo step, the echo step becomes a header in the test. This formatting can help to visually break up different parts of the test in the Trainer window and the Test Details page. More than three hash tags will be grouped to header level three.


Using markdown headers in echo steps

Printing variable values

Echo steps can print the values of variables with mabl variable syntax: {{@variable_name}}. For example, if you want to print the value of a variable called order_total in a test run, write {{@order_total}}.


Use mabl variable syntax in echo steps to print variable values in test output.

When the echo step runs in a local or cloud run, it prints out the value of the referenced variable.


Printing variable values in test output


Referencing missing variables

If an echo step references a variable, but the variable doesn't exist in the test run because it was either deleted or the name changed, the Test Output page prints [not yet evaluated].