Bug Detection

The Bug Detection step automatically identifies application bugs and quality issues in your website.

Overview

Bug Detection analyzes your crawled pages and elements to find:

• Dead links (404 errors)
• Broken pages (errors, crashes)
• Placeholder text left in production
• Empty states that shouldn't be empty
• Form errors and validation issues

Running Bug Detection

Starting Detection

1. Navigate to the Bug Detection step
2. Ensure elements have been extracted
3. Click "Run Bug Detection"
4. Wait for the analysis to complete

Understanding Bugs

Bug Categories

Bug Severity

Bug Status

Viewing Bugs

Bug Summary

The summary panel shows:

• Total bugs found
• Open / Fixed / False-positive counts
• Breakdown by severity
• Breakdown by category

Bug List

Each bug entry displays:

• Title: Brief description
• Page: Where the bug was found
• Severity: Color-coded badge
• Category: Bug type
• Confidence: How certain the detection is (0-100%)

Bug Details

Click a bug to expand and see:

• Description: Detailed explanation
• Evidence: What triggered the detection
• Element: Specific element involved (if applicable)
• Recommendations: Suggested fixes
• Correlated Test: Test that would catch this bug

Managing Bugs

Marking Bugs as Fixed

When you've resolved a bug:

1. Find the bug in the list
2. Click "Mark Fixed"
3. Bug moves to the "fixed" status

Marking False Positives

If a detection is incorrect:

1. Find the bug
2. Click "False Positive"
3. Bug is excluded from counts

This helps QAID learn and reduces future false positives.

Filtering Bugs

Use filters to focus on specific bugs:

• By Status: Open, Fixed, False Positive
• By Severity: Critical, High, Medium, Low
• By Category: Dead link, Broken page, etc.

Bug-Test Correlation

QAID automatically correlates bugs with generated tests:

How It Works

1. Bug is detected on a page
2. QAID finds tests that cover that page/element
3. Bug is linked to relevant test
4. Test is modified to assert the bug (optional)

Viewing Correlations

In the bug details:

• Test File: The test file that covers this area
• Test Name: Specific test case
• Correlation Confidence: How sure QAID is about the match

Injecting Bug Assertions

When enabled, QAID can:

1. Add assertions to existing tests that will fail when the bug exists
2. Create new tests specifically for the bug
3. Track when the test starts passing (bug fixed)

Detection Run History

View previous detection runs:

• Click "History"
• See each run with timestamp and bug count
• Compare runs to track progress

Run Metrics

Each run shows:

• Pages analyzed
• Elements analyzed
• Bugs found
• API cost
• Duration

Best Practices

Regular Detection

• Run bug detection after deployments
• Schedule periodic scans
• Compare results over time

Handling Results

• Address Critical bugs first
• Review false positives to improve detection
• Use bugs to guide test creation

Improving Detection Accuracy

• Complete element extraction first
• Ensure pages are fully rendered
• Mark false positives consistently

Troubleshooting

Too Many False Positives

Possible causes:

• Dynamic content being flagged
• Intentional placeholder text
• User-specific content

Solutions:

• Mark false positives to train the system
• Review detection patterns
• Check if content is genuinely problematic

Bugs Not Being Detected

Possible causes:

• Bug only appears after user interaction
• Affected element hasn't been extracted yet
• Bug in JavaScript-only content

Solutions:

• Use scenario tests for interaction-dependent bugs
• Ensure element extraction is complete
• Check page rendering settings

Correlation Incorrect

If bugs are linked to wrong tests:

• The correlation is based on page URL and element matching
• Mark the correlation as incorrect if available
• Create a more specific test for the bug

Related Topics

• Element Extraction - Required before bug detection
• Diff Analysis - Compare snapshots over time
• Automated Tests - Tests can catch detected bugs