if you need to filter or search tests in repository, both tags and labels are good
if you need to export meta data to csv file, both tags and labels are good
if you need to apply meta data from templates, both tags and labels are good
if you need to use steps extensively, labels are better
if you need to review tests and mark it somehow, labels are better
if you need to categorize tests, tags are better
if you need to combine manual tests with automation tests to check coverage, tags are better
if you need to push context from manual tests to automated tests thru code templates, tags are better
if you need to make test plans based on filtering capabilities, both tags and labels are good
if you need to aggregate the analytic results, both tags and labels are good
etc
so give me more context what you’re trying to achieve ?
filter tests, build test plan, maintain description, etc?
labels are more flexible than tags, they are more modern. So I would probably go with them.
Tags are bound to test case names and suite names which makes them not as easy to apply/change.
But both are fine to use depending on a context. We have never about transforming labels to tags. It could make sense for some cases but for sure I won't recommend to convert ALL labels into tags.
Show more
Direct Message | Yesterday at 01:09 | View reply
if we try to unify some descriptions, it will be something following
Tags
Purpose: To categorize and/or organize tests
Generality: More general
Applications: More for automated tests less for manual
Usage: Less flexible for describing specific details
Use cases: catigorization, filtering, search, test plans, coverage, analytics
Labels
Purpose: To identify meta data related to tests or object
Generality: More specific
Applications More for manual tests, less for automated
Details: Can have complex types, labels can have values, more flexible
Use cases: track the progress, maintain, review, steps, runs, collaboration
https://testomatio.slack.com/archives/C06BA4P2K96/p1703081942571279?thread_ts=1702906285.989959&cid=C06BA4P2K96
I do remembered your our conversation, and I explained to your these concepts, also
described it also here https://testomatio.slack.com/archives/C06BA4P2K96/p1702944579546189?thread_ts=1702906285.989959&cid=C06BA4P2K96, there is no good or bad practices about tags or labels, it purely depends on context, for example:
if you need to aggregate the analytic results, both tags and labels are good etc so give me more context what you’re trying to achieve ? filter tests, build test plan, maintain description, etc?
labels are more flexible than tags, they are more modern. So I would probably go with them. Tags are bound to test case names and suite names which makes them not as easy to apply/change. But both are fine to use depending on a context. We have never about transforming labels to tags. It could make sense for some cases but for sure I won't recommend to convert ALL labels into tags. Show more Direct Message | Yesterday at 01:09 | View reply
if we try to unify some descriptions, it will be something following Tags
Purpose: To categorize and/or organize tests Generality: More general Applications: More for automated tests less for manual Usage: Less flexible for describing specific details Use cases: catigorization, filtering, search, test plans, coverage, analytics Labels Purpose: To identify meta data related to tests or object Generality: More specific Applications More for manual tests, less for automated Details: Can have complex types, labels can have values, more flexible Use cases: track the progress, maintain, review, steps, runs, collaboration