FAQ

Common questions about using QAID.

General Questions

What is QAID?

QAID is an AI-powered E2E test generator that crawls websites, understands page purposes, and generates meaningful Playwright tests. It learns from failures and improves over time.

What types of tests can QAID generate?

QAID generates two primary types of tests:

1. Automated Tests (Scenarios): AI-powered user journey tests based on page purpose
2. Manual Tests: Structured test cases for human execution

Plus Visual Regression testing via screenshot comparison and API Testing for endpoint validation.

What websites can QAID test?

QAID can test any web application accessible via URL:

• Public websites
• Authenticated applications (with credentials)
• Single Page Applications (SPAs)
• Traditional multi-page sites

Does QAID work with my technology stack?

Yes. QAID works at the browser level and is technology-agnostic. It works with:

• React, Vue, Angular
• WordPress, Drupal
• Ruby on Rails, Django
• Any web framework

Is QAID free to use?

QAID has associated costs for AI API usage (Anthropic's Claude). You need an Anthropic API key and will be charged based on token usage.

---

Setup & Configuration

How do I get started?

1. Create a project with your website URL
2. Run page discovery
3. Extract elements
4. Generate tests

See Quick Start for details.

How do I test pages that require login?

1. Go to Project Settings
2. Enable Authentication
3. Enter your credentials (username/password)
4. QAID will log in before crawling

Can I exclude certain pages?

Yes. In the Pages step:

1. Find the page you want to exclude
2. Click the menu (...)
3. Select "Blacklist"

Blacklisted pages won't be crawled or tested.

How do I configure the Chrome extension?

1. Load the QAID Recorder extension via chrome://extensions > "Load unpacked"
2. Enable Developer mode and copy the Extension ID
3. In QAID, click your profile avatar > "Extension API Key"
4. Paste the Extension ID and click Save

---

Page Discovery

Why aren't all my pages being discovered?

Common reasons:

• Max Pages limit reached: Increase the limit
• JavaScript-only navigation: Crawler may miss some SPA routes
• Authentication required: Configure credentials
• Pages blocked by robots.txt: Check site permissions

Can I add pages manually?

Yes. In the Pages step:

1. Click "Add Page"
2. Enter the page path (e.g., /about)
3. Click "Add"

What do the page statuses mean?

---

Element Extraction

Why are some elements not detected?

Elements may not be detected if they:

• Are in Shadow DOM (not supported)
• Require complex multi-step interactions to appear
• Are in cross-origin iframes
• Are loaded asynchronously after initial render

Note: QAID automatically handles elements hidden behind dropdown menus and simple navigation during both crawling and test execution.

How do I improve element detection?

• Add data-testid attributes to key elements
• Use semantic HTML (<button>, <nav>)
• Ensure forms have proper labels
• Wait for full page load before extraction

What are the element importance levels?

---

Test Generation

How does QAID ensure reliable selectors?

QAID only uses selectors from elements that were actually discovered on your site. It never invents or guesses selectors, ensuring tests are reliable.

What is Production-Safe Mode?

When enabled, tests only verify visibility and presence:

• No form submissions
• No button clicks that modify data
• Safe to run against production

Why are my tests failing?

Common causes:

• Site changed since test generation
• Timing issues (element loads slowly)
• Authentication problems
• Selector became invalid

Solutions:

1. Re-run element extraction
2. Regenerate tests
3. Check authentication settings

---

Automated Tests

How do I create a good scenario?

Write clear descriptions of user goals:

• "User should be able to submit contact form"
• "User navigates from homepage to pricing"

Avoid vague descriptions:

• "Test the form" (too vague)
• "Click button" (no goal)

Why does my scenario have missing elements?

The AI may need elements that:

• Changed since last extraction
• Are in cross-origin iframes
• Require complex multi-step interactions

QAID's runtime element discovery automatically handles elements hidden behind dropdown menus and navigation during test execution. If elements are still missing, re-run element extraction and regenerate the scenario.

---

Visual Regression

What is visual regression testing?

Visual regression compares screenshots over time:

1. Capture a "baseline" screenshot
2. Later, capture a new screenshot
3. Compare pixel-by-pixel
4. Flag differences

When should I use Record & Snap?

Use it when the page requires setup:

• Login pages
• Modal dialogs
• Specific scroll positions
• After form submission

Why am I getting false positives?

Common causes:

• Dynamic content (timestamps, dates)
• A/B testing
• User-specific content
• Animations captured mid-frame

Solutions:

• Increase wait time
• Adjust threshold
• Use Record & Snap for consistent states

---

Test Execution

How do I run tests?

From the Test Plan step:

1. Select tests (or "Run All")
2. Click "Run"
3. Watch execution progress
4. View results

Where can I see test results?

• Inline: In the Test Plan details panel
• Playwright Report: Full HTML report with traces
• Dashboard: Summary metrics

Can I run tests on CI/CD?

Yes. Export your Playwright tests and run them in your CI/CD pipeline using standard Playwright commands.

---

Costs & Usage

How much does QAID cost to use?

QAID costs depend on AI API usage (Anthropic Claude). Costs vary based on the complexity of your site and how many tests you generate.

How do I reduce AI costs?

• Limit pages during initial testing
• Enable Production-Safe Mode
• Use fewer concurrent test executions

Where can I see my AI usage?

AI cost tracking is available on the Enterprise tier via Admin > API Usage. It shows usage trends and total cost over time.

---

Troubleshooting

Tests were working but now fail

1. Check if the site changed
2. Re-run element extraction
3. Regenerate affected tests
4. Verify authentication still works

QAID is slow

• Reduce Max Pages limit
• Lower crawl depth
• Check your network connection
• Consider fewer concurrent operations

Extension not working

1. Verify Extension ID is correct
2. Check extension is enabled
3. Grant required permissions
4. Restart browser

See Troubleshooting for more detailed solutions.

---

Best Practices

What's the recommended workflow?

1. Start with 20-30 pages
2. Extract elements
3. Review quality issues and bugs
4. Generate automated test scenarios for critical flows
5. Set up visual baselines
6. Organize in Test Plan
7. Run regularly

How often should I update tests?

• After deployments
• When UI changes
• When tests start failing
• Weekly maintenance review

How do I maintain test quality?

• Keep tests focused and simple
• Use meaningful names
• Review failing tests promptly
• Update for intentional changes
• Remove obsolete tests

---

More Help

• Glossary - Key terms explained
• Troubleshooting - Common issues
• Documentation home - Browse all guides