Skip to main content

Overview

Tags provide a flexible way to categorize tests across your folder structure. Unlike folders which provide hierarchical organization, tags allow tests to belong to multiple categories simultaneously, making it easy to filter and find related tests.

Why Use Tags

Tags complement folder organization:
FoldersTags
Hierarchical (one parent)Flat (multiple tags per test)
Physical groupingLogical categorization
Move tests betweenAdd/remove without moving
Best for ownershipBest for attributes
Example: A test in the Checkout folder might have tags: smoke, p0, payments, regression

Creating Tags

Add Tags to a Test

  1. Open a test case in the editor
  2. Click the Tags field in the test details panel
  3. Type a tag name
  4. Press Enter or select from suggestions
  5. Repeat to add multiple tags

Tag Naming

Follow consistent naming conventions:
CategoryExamples
Priorityp0, p1, p2, critical, high, low
Typesmoke, regression, e2e, integration
Featureauth, payments, search, notifications
Statusflaky, needs-review, stable, wip
Platformmobile, desktop, api
Tips:
  • Use lowercase for consistency
  • Keep tags short and memorable
  • Avoid spaces (use hyphens instead)
  • Create a team tag vocabulary

Managing Tags

View All Tags

Access your tag library:
  1. Go to Settings > Tags (or filter panel)
  2. View all tags in use
  3. See test counts per tag

Edit Tags

Modify existing tags:
  1. Open a test with the tag
  2. Click on the tag to edit
  3. Update the tag name
  4. Changes apply to all tests with that tag

Remove Tags

Remove a tag from a test:
  1. Open the test case
  2. Click the X on the tag
  3. Tag is removed from this test only
To delete a tag entirely:
  1. Remove it from all tests, or
  2. Delete from tag management settings

Filtering by Tags

Quick Filter

Use the Test Explorer filter:
  1. Click the Filter icon
  2. Select Tags
  3. Choose one or more tags
  4. View filtered results

Advanced Filtering

Combine multiple filters:
  • AND: Tests must have all selected tags
  • OR: Tests must have any selected tag
  • NOT: Exclude tests with specific tags
Example filters:
tags: smoke AND p0
→ All P0 smoke tests

tags: regression OR e2e
→ All regression and E2E tests

tags: auth NOT flaky
→ Auth tests excluding flaky ones

Search with Tags

Use the search bar:
tag:smoke
tag:p0 tag:payments
-tag:flaky

Tag Strategies

By Test Priority

Assign priority levels:
p0 - Critical path, run on every deploy
p1 - Important flows, run daily
p2 - Extended coverage, run weekly
p3 - Edge cases, run periodically

By Test Type

Categorize test purpose:
smoke - Quick health checks
regression - Full feature coverage
e2e - End-to-end user journeys
integration - API and service tests
visual - UI appearance tests

By Feature Area

Tag by product domain:
auth - Authentication tests
payments - Payment processing
search - Search functionality
notifications - Alert systems
admin - Admin panel tests

By Test Health

Track test reliability:
stable - Consistently passes
flaky - Intermittent failures
needs-fix - Known issues
new - Recently added

By Execution Context

Specify when/where tests run:
ci - Run in CI pipeline
nightly - Run in nightly builds
manual - Require manual trigger
staging - Staging environment only
prod - Production checks

Using Tags with Test Plans

Schedule by Tags

Create test plans that run tests by tag:
  1. Create a new test plan
  2. Select Add by Tag
  3. Choose the tags to include
  4. Tests matching tags are added automatically
Example plan configurations:
Smoke Test Plan:
  Tags: smoke, p0
  Schedule: Every deploy

Nightly Regression:
  Tags: regression
  Schedule: Daily at 2am

Payment Tests:
  Tags: payments
  Schedule: Before releases

Dynamic Test Plans

Tag-based plans update automatically:
  • New tests with matching tags are included
  • Removed tags exclude tests from plan
  • No manual plan updates needed

Best Practices

Create a Tag Vocabulary

Define standard tags for your team:
# Team Tag Standards

## Priority (required)
- p0: Critical, blocks release
- p1: High priority, fix soon
- p2: Medium priority
- p3: Low priority

## Type (required)
- smoke: Quick validation
- regression: Full coverage
- e2e: User journey

## Feature (recommended)
- auth, payments, search, etc.

## Status (as needed)
- flaky, stable, wip

Keep Tags Consistent

  • Use the same tag across similar tests
  • Avoid synonyms (pick auth OR authentication, not both)
  • Review and clean up tags periodically
  • Document tag meanings for the team

Don’t Over-Tag

  • Apply 3-5 relevant tags per test
  • Avoid redundant tags
  • Remove outdated tags
  • Focus on actionable categories

Troubleshooting

Tags Not Appearing

  • Verify tag was saved (not just typed)
  • Check for typos in tag name
  • Refresh the Test Explorer

Filter Not Working

  • Ensure correct filter logic (AND vs OR)
  • Check tag spelling matches exactly
  • Clear filters and re-apply

Too Many Tags

  • Audit and consolidate similar tags
  • Remove unused tags
  • Create tag guidelines for team