Muting your tests

If one of your tests is outdated or is no longer relevant, you can mute it so it is not replayed in your next runs.

Why mute a flow?

The purpose of muting a testtest - A test is a flow combined with a set of assertions that define the criteria for acceptance. is to prevent it from being replayed in your runs either temporarily or permanently. This feature is useful when the flowflow - A flow is a sequence of interactions (tap, swipe, etc.) that defines a user journey in an application. A flow can start either at application launch from a pristine state (fresh install) or from the last step of another flow. In the first case, the application is launched in a pristine state from a fresh install. In the second case, the other (preceding) flow is called a dependent flow. is no longer relevant or when you are making big changes to your application and you would like to finalize them before updating the test.

A muted test will no longer appear in the list of possible dependencies for a new test and won't be selectable when manually launching a run.

However, keep in mind that if the muted test is a dependency of another active test, it will still be replayed and will appear in the results.

All your muted tests will be accessible in the Muted tab of your list of tests. There you can view them and unmute them if necessary.

How to mute a test

Muting a test is very simple:

  • Go to your list of tests and find the test you would like to mute.
  • Click the button at the top right of your test to display the menu.
  • In the menu that appears, select Mute.

Your test should now be muted and should appear in the Muted tab. It will no longer be replayed.

How to unmute a test

Unmuting a test is as simple as muting a flow:

  • Go to your tests list and click on the Muted tab.
  • Find the muted test you would like to unmute and click the menu.
  • In the menu that appears, select Unmute.

Your test should now appear in the Active tab of your tests list.