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
- From the home screen, click "New Project"
- Enter a Project Name (e.g., "My Website Tests")
- Enter the Base URL (e.g.,
https://example.com)- Include the protocol (
https://) - Do not include trailing slashes
- Include the protocol (
- Click "Create Project"
Step 2: Configure Authentication (Optional)
If your site requires login:
- Click the Settings icon on your project
- Enable "Requires Authentication"
- Select authentication type:
- Basic Auth: Enter username and password
- Save settings
QAID will use these credentials when crawling protected pages.
Step 3: Discover Pages
- Navigate to the Pages step in the sidebar
- Click "Discover Pages"
- Configure crawl parameters:
- Max Pages: Limit pages to discover (1-200, default 50)
- Max Depth: How deep to follow links (1-10, default 3)
- 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:
- In the Discovery (Pages) step, click "Extract Elements"
- QAID will visit each page and capture:
- Buttons and links
- Form inputs (text, select, checkbox, etc.)
- Interactive components
- Iframe content
- Bug detection runs automatically after extraction
Step 5: Generate Automated Tests (Primary)
This is the main test generation step:
- Go to Automated Tests in the sidebar
- You'll see a list of your crawled pages
- Click on a page to view/create scenarios
- Click "Generate Scenarios" to have AI suggest test scenarios based on the page's purpose
- Or click "New Scenario" to manually describe a user journey
- 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
- Go to Test Plan step
- View all generated tests in a tree structure
- Create folders to organize tests
- Drag and drop to rearrange
- Use AI Organize for automatic grouping by priority, page, or feature
Step 7: Run Tests
- Go to Test Run in the sidebar
- Click "Start Run"
- Select a test plan to execute
- Configure parallel tests (1-5)
- Watch execution progress in real-time
- View pass/fail results when complete
Step 8: Review Results
- Go to Analysis to see test health trends
- Pass rate trends across runs
- Flaky test identification
- Consistently failing tests
- Go to Dashboard (Overview) for the quality score and summary
- Go to Actions for AI-powered recommendations on what to improve next
Quick Reference: Workflow Progression
| You Want To... | Do This |
|---|---|
| Find all pages | Discovery -> Discover Pages |
| See page elements | Discovery -> Extract Elements |
| Create journey tests | Automated Tests -> Click page -> Generate Scenarios |
| Record a test | Install Chrome extension -> Record & Snap |
| Compare screenshots | Visual Regression -> Capture Baseline |
| Get manual test cases | Manual Tests -> Generate |
| Organize everything | Test Plan -> Create folders or AI Organize |
| Execute tests | Test Run -> Start Run |
| See test trends | Analysis -> Review pass rates and flaky tests |
| Get recommendations | Actions -> 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
- Page Discovery - Learn about advanced page management
- Automated Tests - Create powerful user journey tests
- Test Runs - Execute and monitor test plans
- Visual Regression - Set up screenshot testing
- Chrome Extension - Record user interactions