Skip to content

Latest commit

 

History

History
18 lines (11 loc) · 1.03 KB

tags.mdx

File metadata and controls

18 lines (11 loc) · 1.03 KB
title Tags
description Group flows under a name so a trigger can run them together and a Run Rule can order or co-schedule them.

How tags work

A tag names a group of flows so other features can select them. A trigger can run every flow carrying a tag, and a Run Rule can order or co-schedule flows by tag. A trigger that names a tag picks up every flow tagged later, so tagging a new flow adds it to that trigger's runs. Draft and in-maintenance flows are left out.

Triggers and rules.yaml refer to a tag by its name. Renaming a tag disconnects it from the triggers that name it, and leaves a rules.yaml that names it invalid.

Tags exist at the Workspace level, can be applied to any flow, and are available to all users in your workspace.

FAQ

What tags should I create?

Common tags include test type (e.g., sanity or smoke) and expected duration (e.g., long-running). Since QA Wolf runs all tests in parallel by default, you do not need to use tags to shard your flows.