Tag-Based Filtering

Master the art of focused test analysis using tag-based filtering to drill down into specific test subsets and uncover actionable insights.

How It Works

Important: Tag-based filtering in the Reports dashboard affects display views only - all KPI calculations remain project-wide for consistency.

Default View: All Tests - By default, the Test Insights section shows all tests in your project with project-wide KPIs.
Apply Tag Filters - Select one or more tags to filter which tests are displayed in the Test Insights section.
Display Updates - The test count and display views update to show only filtered tests, but all KPIs remain project-wide for accurate reporting.

Common Tag Patterns

Test Types

Use these tags to filter by testing strategy:

@smoke - Quick validation tests
@regression - Full feature regression tests
@integration - Service integration tests
@e2e - End-to-end user journey tests

Use Case: Filter by @smoke to analyze your critical path tests and ensure they maintain 100% pass rates.

Priority Levels

Focus on tests by business importance:

@critical - Must-pass tests for core functionality
@high - Important feature tests
@medium - Standard feature coverage
@low - Nice-to-have test coverage

Use Case: Monitor @critical tests separately to ensure your most important functionality is always working.

Feature Areas

Analyze specific parts of your application:

@auth - Authentication and authorization
@payment - Payment processing flows
@dashboard - Dashboard functionality
@api - API endpoint testing

Use Case: Filter by @payment to track the reliability of your revenue-critical functionality.

Environment Tags

Compare performance across different contexts:

@staging - Staging environment tests
@production - Production validation tests
@mobile - Mobile-specific tests
@desktop - Desktop browser tests

Use Case: Use @mobile vs @desktop to compare performance across platforms.

Advanced Filtering Techniques

Multi-Tag Selection

Select multiple tags to create intersections and analyze specific combinations:

Example: @critical + @auth

Shows only critical authentication tests
Helps ensure your most important login flows are bulletproof

Example: @smoke + @regression

Analyzes tests that serve both purposes
Identifies overlap in your testing strategy

Performance Analysis

Use filtering to identify performance patterns:

Filter by @slow to find tests needing optimization
Use @flaky to analyze unreliable tests
Apply @new to monitor recently added tests

Quality Monitoring

Track quality metrics for specific test categories:

Monitor @critical tests for 100% pass rates
Track @nightly tests for maintenance needs
Analyze @api tests for performance trends

What Changes When Filtering

When you apply tag filters, the Reports dashboard updates the display while maintaining consistent KPIs:

Test Count Display

The "Test Count" metric shows the number of tests matching your selected tags.

Test List Views

Only tests matching the selected tags are shown in any test listings or detailed views.

Contextual Hints

Tooltips update to clarify that you're viewing a filtered subset of tests.

What Stays the Same

All KPI calculations remain project-wide:

Pass Rate: Always shows project-wide success rate
Health Scores: Based on entire project performance
Automation Coverage: Project-wide enabled/disabled ratios
Performance Metrics: Calculated from all project tests

This ensures consistent and accurate reporting across all dashboard sections.

Best Practices

Start Broad, Then Narrow

Begin with broad filters like @critical or @smoke to get an overview
Add more specific tags to drill down into problem areas
Clear all filters periodically to maintain perspective on overall test health

Use Filters for Investigation

When you notice issues in the overall metrics:

Apply relevant tags to focus on specific test subsets in the display
Review which tests are affected while understanding that KPIs reflect project-wide health
Use the filtered view to identify specific tests needing attention while maintaining perspective on overall project performance

Monitor Key Combinations

Set up regular reviews of important tag combinations to focus your analysis:

@critical + @flaky - View critical tests that may need immediate attention
@new + @failed - Focus on recently added tests that aren't working
@slow + @regression - Identify performance bottlenecks in regression suite

Remember: These filters help you focus on specific test subsets, but KPIs always reflect project-wide health for accurate reporting.

Filter Management Tips

Clear Filters Regularly: Don't lose sight of your overall test health
Document Tag Conventions: Ensure your team uses consistent tagging
Review Filter Results: Validate that filtered metrics make sense
Combine with Time Periods: Use filtering alongside date ranges for trend analysis

The tag-based filtering system transforms the Reports dashboard into a powerful analytical tool that lets you focus on specific test subsets while maintaining consistent, project-wide KPI calculations for accurate reporting and decision-making.