Skip to content
Marriska Docs

Organize and run tests with tags

Tags are freeform labels you stick on tests: smoke, checkout, flaky, release-blocker. A test can carry several. Unlike folders (where a test lives in exactly one place) tags are many-to-many and org-wide — they cross projects and folders. That’s what makes them the right tool for “run every smoke test, wherever it lives.”

Create a tag

Section titled “Create a tag”

Tags live in the Tags panel on the Tests page.

  1. Open the panel. Select one or more tests (the checkboxes in the explorer) and click Tags in the bulk action bar — or right-click a single test and choose Tags.

  2. Click “New tag”. Type a name and pick a color from the palette. The name has to be unique within your org.

  3. Save. The tag is created and immediately available to assign.

Each tag’s chip color is what you’ll see throughout the app, and the text auto-switches between black and white so it stays readable in both light and dark mode.

Assign tags to tests

Section titled “Assign tags to tests”

The same panel handles assignment, and it works on a whole selection at once.

With one or more tests selected, the panel shows two columns:

  • Available — tags not yet on the selection. Click one to add it.
  • Added — tags currently on the selection. Click one to remove it.

If a tag is on some but not all of the selected tests, it’s marked some — click it to apply it to the rest. This is the fast way to tag a dozen tests smoke in one go.

Filter the Tests page by tag

Section titled “Filter the Tests page by tag”

In the explorer sidebar, below the search box, there’s a Filter by tag dropdown (it only appears once you have tags). Pick one or more tags and the tree narrows to matching tests.

Multiple tags are an OR filter: pick smoke and checkout and you see every test carrying either. Hit Clear to drop the filter.

Run every test with a tag

Section titled “Run every test with a tag”

This is the payoff. On the Runner page, the sidebar has a Run by tag section.

  1. Pick a tag from the dropdown.

  2. Click Run. A run-config popover opens — choose your browsers and, if you have a local agent connected, Cloud or Local. Then Run now.

Running by tag gathers every test carrying that tag across all your projects and runs them as one batch, labeled Tag: <name>. It’s not scoped to the project you’re looking at — a tag is org-wide, so the run is too. If no test carries the tag, you’ll get a heads-up toast and nothing runs.

Tags vs. folders vs. test sets

Section titled “Tags vs. folders vs. test sets”

These three overlap in people’s heads. They don’t overlap in the app:

What it isScopeA test can be in…
TagA freeform labelOrg-widemany tags
FolderA spot in the project treeOne projectone folder
Test setA named, runnable groupOne projectmany sets

Reach for a tag when the grouping is a cross-cutting concern (smoke, flaky) that ignores where the test is filed. Reach for a folder to file a test in one tidy place. Reach for a test set when you want to run a fixed group together, in order, on a schedule.

Limits

Section titled “Limits”

Tags are unlimited on every plan, Free included. Make as many as help.

Section titled “Related”