QAID Docs

Quick Start

Create your first QAID project and generate your first tests.

This guide walks you through creating your first project and generating tests.

Prerequisites

Before starting, ensure you have:

  • A website URL you want to test
  • (Optional) Login credentials if testing authenticated areas
  • (Optional) Chrome browser with the QAID extension for recording

Creating Your First Project

Step 1: Create a New Project

  1. From the home screen, click "New Project"
  2. Enter a Project Name (e.g., "My Website Tests")
  3. Enter the Base URL (e.g., https://example.com)
    • Include the protocol (https://)
    • Do not include trailing slashes
  4. Click "Create Project"

Step 2: Configure Authentication (Optional)

If your site requires login:

  1. Click the Settings icon on your project
  2. Enable "Requires Authentication"
  3. Select authentication type:
    • Basic Auth: Enter username and password
  4. Save settings

QAID will use these credentials when crawling protected pages.

Step 3: Discover Pages

  1. Navigate to the Pages step in the sidebar
  2. Click "Discover Pages"
  3. Configure crawl parameters:
    • Max Pages: Limit pages to discover (1-200, default 50)
    • Max Depth: How deep to follow links (1-10, default 3)
  4. Click "Start Discovery"

Watch as QAID finds pages across your site. The discovery:

  • Finds links in navigation menus
  • Follows internal links
  • Handles JavaScript-rendered content
  • Respects page limits

Step 4: Extract Elements

Element extraction is part of the Discovery step:

  1. In the Discovery (Pages) step, click "Extract Elements"
  2. QAID will visit each page and capture:
    • Buttons and links
    • Form inputs (text, select, checkbox, etc.)
    • Interactive components
    • Iframe content
  3. Bug detection runs automatically after extraction

Step 5: Generate Automated Tests (Primary)

This is the main test generation step:

  1. Go to Automated Tests in the sidebar
  2. You'll see a list of your crawled pages
  3. Click on a page to view/create scenarios
  4. Click "Generate Scenarios" to have AI suggest test scenarios based on the page's purpose
  5. Or click "New Scenario" to manually describe a user journey
  6. Fill in:
    • Description: What should happen (e.g., "User submits contact form")
    • Expected Result: What success looks like
    • Tags: Categorization labels

Step 6: Organize with Test Plan

  1. Go to Test Plan step
  2. View all generated tests in a tree structure
  3. Create folders to organize tests
  4. Drag and drop to rearrange
  5. Use AI Organize for automatic grouping by priority, page, or feature

Step 7: Run Tests

  1. Go to Test Run in the sidebar
  2. Click "Start Run"
  3. Select a test plan to execute
  4. Configure parallel tests (1-5)
  5. Watch execution progress in real-time
  6. View pass/fail results when complete

Step 8: Review Results

  1. Go to Analysis to see test health trends
    • Pass rate trends across runs
    • Flaky test identification
    • Consistently failing tests
  2. Go to Dashboard (Overview) for the quality score and summary
  3. Go to Actions for AI-powered recommendations on what to improve next

Quick Reference: Workflow Progression

You Want To...Do This
Find all pagesDiscovery -> Discover Pages
See page elementsDiscovery -> Extract Elements
Create journey testsAutomated Tests -> Click page -> Generate Scenarios
Record a testInstall Chrome extension -> Record & Snap
Compare screenshotsVisual Regression -> Capture Baseline
Get manual test casesManual Tests -> Generate
Organize everythingTest Plan -> Create folders or AI Organize
Execute testsTest Run -> Start Run
See test trendsAnalysis -> Review pass rates and flaky tests
Get recommendationsActions -> Generate Actions

Tips for Better Results

Page Discovery

  • Start with a smaller max pages limit (20-30) for initial testing
  • Increase depth if you have deep navigation structures
  • Review discovered pages and blacklist irrelevant ones (admin, logout, etc.)

Element Extraction

  • Wait for full extraction before generating tests
  • Review the detected issues section for bugs found
  • High-quality elements produce better tests

Automated Tests

  • Be specific in scenario descriptions
  • Include expected outcomes
  • Focus on user journeys, not individual elements
  • Let AI generate scenarios first, then customize as needed

Authentication

  • Test login manually first to ensure credentials work
  • Check that the crawler can access protected pages
  • Use session-based auth for complex login flows

Next Steps

On this page