-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
We need to update the documentation for Tags to clearly explain how tags behave at both the suite level and the test level.
📄 Related documentation page:
https://docs.testomat.io/advanced/tags-labels/tags and https://docs.testomat.io/advanced/tags-labels/labels-and-custom-fields/
Problem
There is a common misunderstanding among users regarding tag behavior.
Typical scenario:
- A test has a specific tag.
- The user removes the tag from an individual test and saves changes.
- However, the tag is still displayed.
- The reason: the tag is applied at the suite level, so it is inherited by all tests inside the suite.
Users often do not realize that removing a tag from a single test is not enough if the tag is assigned to the parent suite.
Required Documentation Improvements
The documentation should clearly explain:
-
Tag inheritance logic
- Tags applied to a suite are automatically inherited by all tests inside that suite.
- If a tag exists on the suite, removing it from a single test will not remove it completely.
-
How to properly remove a tag from a single test
-
If a tag is assigned at the suite level and should not apply to one specific test:
- The tag must be removed from the suite.
- Then re-applied manually (or via bulk multi-select) to all other tests except the one that should not have it.
-
-
Bulk tag management
- Clarify that users can use multi-select to add tags in bulk instead of editing tests one by one.
- To do so they need to switch to multiselect tests mode
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels