Manual Tests

The Manual Tests step generates structured manual test cases that humans can execute.

Overview

Not all testing should be automated. Manual Tests provides:

• Structured test cases with clear steps
• Human-readable test plans
• Coverage for areas hard to automate
• Test documentation for QA teams
• Exportable test plans

Generating Manual Tests

Starting Generation

1. Navigate to the Manual Tests step
2. Click "Generate Manual Tests"
3. If tests already exist, confirm regeneration
4. Wait for AI to generate test cases

Generation Process

QAID analyzes each page and creates test cases based on:

• Page purpose and functionality
• Available interactive elements
• Common user workflows
• Accessibility requirements
• Edge cases and error scenarios

Test Plan Structure

Test Plan Overview

The generated plan includes:

• Total Test Cases: Number of tests generated
• Priority Breakdown: Critical, High, Medium, Low counts
• Category Breakdown: Functional, Usability, Accessibility, Edge-case counts
• Automation Status: Which tests could be automated

Test Case Details

Each test case contains:

• Title: Brief description of what's being tested
• Description: Detailed explanation
• Priority: Critical, High, Medium, or Low
• Category: Type of test
• Preconditions: Setup required before testing
• Test Steps: Numbered actions with expected results
• Expected Result: Overall success criteria
• Test Data: Any specific data needed

Test Categories

Functional Tests

Verify features work as expected:

• Forms submit correctly
• Navigation works
• Buttons perform actions
• Data displays properly

Usability Tests

Evaluate user experience:

• Flow is intuitive
• Labels are clear
• Error messages are helpful
• Actions are discoverable

Accessibility Tests

Check for accessibility compliance:

• Screen reader compatibility
• Keyboard navigation
• Color contrast
• Focus indicators

Edge-Case Tests

Test boundary conditions:

• Empty inputs
• Maximum length inputs
• Invalid data
• Concurrent actions

Test Priorities

Viewing Test Cases

Test List View

See all tests in a list:

• Title with priority badge
• Category badge
• Expandable details
• Filter and search

Expanded View

Click a test to see full details:

Title: User can submit contact form
Priority: High
Category: Functional

Preconditions:
- User is on the Contact page
- User is not logged in

Steps:
| # | Action | Expected Result |
|---|--------|-----------------|
| 1 | Enter name in Name field | Name accepted |
| 2 | Enter email in Email field | Email accepted |
| 3 | Enter message in Message field | Message accepted |
| 4 | Click Submit button | Form submits |
| 5 | Observe confirmation | Success message shown |

Expected Result:
Form submits successfully and confirmation message displays

Test Data:
{
  "name": "Test User",
  "email": "test@example.com",
  "message": "Test message"
}

Filtering Tests

By Priority

• Click priority filter buttons
• Select one or more priorities
• View matching tests

By Category

• Click category filter buttons
• Select one or more categories
• View matching tests

By Search

• Enter text in search box
• Matches against title and description
• Real-time filtering

Exporting Test Plans

Export as CSV

1. Click "Export"
2. Select CSV format
3. Download file

CSV includes all fields:

• Title, Description, Priority, Category
• Preconditions, Steps, Expected Result
• Test Data

Using Exports

Import into:

• Test management tools (TestRail, Zephyr)
• Spreadsheet applications
• Documentation systems
• Project management tools

Test Execution Tracking

Manual Tracking

While QAID doesn't track manual test execution directly, you can:

• Export tests to tracking tools
• Use test data in external systems
• Reference tests by ID

Correlation with Automated Tests

Many manual tests can eventually be automated:

• Review automation status
• Create scenarios from manual test steps
• Track which tests have automated equivalents

Regenerating Tests

When to Regenerate

• After significant site changes
• When new pages are added
• After element extraction updates
• To get fresh AI analysis

Regeneration Process

1. Click "Generate Manual Tests"
2. Confirm you want to replace existing tests
3. New tests are generated
4. Old tests are replaced

Warning: This replaces all existing manual tests.

Per-Page Generation

Generate tests for specific pages:

1. Select a specific page
2. Click "Generate for Page"
3. Only that page's tests are regenerated
4. Other tests remain unchanged

Best Practices

Test Case Quality

• Keep steps clear and concise
• One action per step
• Specific expected results
• Realistic test data

Coverage Planning

• Prioritize critical paths
• Include negative test cases
• Cover accessibility requirements
• Test edge cases

Maintenance

• Review tests after site changes
• Update test data periodically
• Remove obsolete tests
• Keep priorities current

Generation Metadata

View information about the generation:

• Timestamp: When tests were generated
• Pages Analyzed: Number of pages reviewed
• API Cost: Cost of the generation
• Model Used: AI model that generated tests

Troubleshooting

No Tests Generated

Possible causes:

• No pages discovered
• No elements extracted
• Generation failed

Solutions:

• Complete page discovery first
• Run element extraction
• Check for error messages

Tests Don't Match Site

Possible causes:

• Elements changed since generation
• Site updated
• Stale data

Solutions:

• Run element extraction again
• Regenerate tests
• Check generation timestamp

Missing Test Categories

Possible causes:

• Limited page functionality
• No forms/interactive elements
• Simple page structure

This is normal for pages with limited functionality.

Export Issues

CSV formatting problems:

• Check for special characters in test data
• Verify encoding (UTF-8)
• Try different import settings

Related Topics

• Element Extraction - Required before generation
• Automated Tests - Automated alternative
• Test Plan - Organize all tests together