Labels

As your workspace grows, labels help keep your workspace organized, making it easier to review activity and create a more efficient testing workflow. This article explains the role of plan, test, and flow labels in your mabl workspace.

Searching a workspace by label

Plan labels

Plan labels are useful for defining test suites, such as “regression”, “targeted regression”, “smoke”, or a certain functionality or feature area. If you want to integrate mabl tests into your CI/CD pipeline, you can leverage plan labels to run a set of plans in tandem as a mabl deployment event. To get the most out of your plan labels, work with your team to align on the plan labels that make sense for your workflow.

Plan labels are added and removed on the edit plan page.

Test labels

Test labels are useful for organizing additional groupings of tests in your workspace, such as tests that validate search functionality or tests that require review. After your team establishes a good labeling practice, you can leverage test labels to quickly identify a set of relevant tests in your workspace or run specific tests from the mabl CLI.

The following table gives examples of different types of test labels and examples that a team might use:

Test labels are managed in the test information modal.

You can also add test labels in bulk on the tests page.

Flow labels

You can also use flow labels to organize and quickly identify flows in your workspace. The mabl Trainer supports the following syntax for searching flows to import by label: “label:{label_name}”. For example, if you want to find flows with the label “login”, you can type “label:login” in the search input.

Flow labels are managed in the flow information modal.