Scoutqa-Test

# ScoutQA Testing Skill

Perform AI-powered exploratory testing on web applications using the `scoutqa` CLI.

**Think of ScoutQA as an intelligent testing partner** that can autonomously explore, discover issues, and verify features. Delegate testing to multiple parallel ScoutQA executions to maximize coverage while saving time.

When to Use This Skill

Use this skill in two scenarios:

1. **User requests testing** - When the user explicitly asks to test a website or verify functionality

2. **Proactive verification** - After implementing web features, automatically run tests to verify the implementation works correctly

**Example proactive usage:**

- After implementing a login form → Test the authentication flow

- After adding form validation → Verify validation rules and error handling

- After building a checkout flow → Test the end-to-end purchase process

- After fixing a bug → Verify the fix works and didn't break other features

**Best practice**: When you finish implementing a web feature, proactively start a ScoutQA test in the background to verify it works while you continue with other tasks.

Running Tests

Testing Workflow

Copy this checklist and track your progress:

Testing Progress:

- [ ] Write specific test prompt with clear expectations

- [ ] Run scoutqa command in background

- [ ] Inform user of execution ID and browser URL

- [ ] Extract and analyze results

**Step 1: Write specific test prompt**

See "Writing Effective Prompts" section below for guidelines.

**Step 2: Run scoutqa command**

**IMPORTANT**: Use the Bash tool's timeout parameter (5000ms = 5 seconds) to capture execution details:

When calling the Bash tool, set `timeout: 5000` as a parameter:

- This is the Bash tool's built-in timeout parameter in Claude Code (NOT the Unix `timeout` command)

- After 5 seconds, the Bash tool returns control with a task ID and the process continues running in the background

- This is different from Unix `timeout` which kills the process - here the process keeps running

- The first 5 seconds capture the execution ID and browser URL from ScoutQA's output

- The test continues running remotely on ScoutQA's infrastructure with the background task

scoutqa --url "https://example.com" --prompt "Your test instructions"

In the first few seconds, the command will output:

- **Execution ID** (e.g., `019b831d-xxx`)

- **Browser URL** (e.g., `https://app.scoutqa.ai/t/019b831d-xxx`)

- Initial tool calls showing test progress

After the 5-second timeout, the Bash tool returns a task ID and the command continues running in the background. You can work on other tasks while the test runs. The timeout is only to capture the initial output (execution ID and browser URL) - the test keeps running both locally as a background task and remotely on ScoutQA's infrastructure.

**Step 3: Inform user of execution ID and browser URL**

After the Bash tool returns with the task ID (having captured the execution details in the first 5 seconds), inform the user of:

- The ScoutQA execution ID and browser URL so they can monitor progress in their browser

- The background task ID if they want to check local command output later

The test continues running in the background while you continue other work.

**Step 4: Extract and analyze results**

See "Presenting Results" section below for the complete format.

Command Options

- `--url` (required): Website URL to test (supports `localhost` / `127.0.0.1`)

- `--prompt` (required): Natural language testing instructions

- `--project-id` (optional): Associate with a project for tracking

- `-v, --verbose` (optional): Show all tool calls including internal ones

Local Testing Support

ScoutQA supports testing `localhost` and `127.0.0.1` URLs autonomously — no manual setup required.

# Seamlessly test a locally running app when you're developing your app
scoutqa --url "http://localhost:3000" --prompt "Test the registration form"

When to Use Each Command

**Sta