Documentation

# coTestPilot Docs

AI-powered testing copilot for manual testers. Find bugs faster, generate test cases, and file them in seconds — right from your browser sidebar.

🚀 Jump to Quick Start

Getting Started

## 🚀 Quick Start

Get up and running in under 2 minutes.

1

#### Open the sidebar

Click the coTestPilot icon in your Chrome toolbar. The sidebar opens alongside the page you're testing — no redirects, no new windows.

2

#### Navigate to any page

Go to the page you want to test. coTestPilot automatically scans it and populates Test Cases, Analyze, and Likely Bugs tabs within seconds.

3

#### Inspect an element

Click Element in the Inspect section, then hover and click any element on the page. coTestPilot captures its selector, attributes, and runs AI analysis on it instantly.

4

#### File your first bug

Switch to the Report tab (or click Create Bug Report from any AI result). Fill in the title, attach a screenshot, and hit File Bug — it goes straight to JIRA, GitHub, or your configured tracker.

🦺 On your first launch, coTestPilot auto-detects your browser language and runs an analysis of the current page. By the time you've read the tab titles, results are already there.

Getting Started

## 🗺 Overview

coTestPilot lives in your browser sidebar. It has two main tabs:

- Test — inspect elements, run AI analysis, fill forms, manage test cases, and take notes
- Settings — configure AI provider, bug tracker integrations, context snippets, language, and appearance

🔍
Element Inspection
Click any element to capture its CSS selector, XPath, role, attributes, and computed state. AI analysis runs in parallel.
🤖
AI Analysis
Three auto-running analyses per page: Test Cases, Page Analysis, and Likely Bugs. Results appear in seconds.
🐛
Bug Reporting
File bugs to JIRA, GitHub Issues, Linear, or Azure DevOps — with screenshot and page URL auto-attached.
📝
Form Assistant
Fill every field with realistic test data in one click. Triggers React/Vue events so the page responds correctly.
✅
Test Execution
Run generated test cases directly in the page. Get instant Pass/Fail results — no test framework needed.
🌐
Multi-language UI
English, Hindi, Mandarin, and Spanish. Auto-detects your browser language on first launch.

Features

## 🔍 Inspect

The Inspect section gives you three ways to capture information from the page.

### Element mode

Click Element, then click any element on the page. coTestPilot captures:

- CSS selector and XPath
- Element tag, ID, classes, visible text
- ARIA role and accessibility attributes
- AI-ranked selector alternatives (most stable → least stable)
- AI analysis: test suggestions, accessibility issues, selector robustness

### Screen mode

Click Screen to capture a full screenshot of the current viewport. The screenshot is attached to subsequent AI calls and can be included in bug reports.

### Draw mode

Click Draw to annotate the page with freehand drawings. Use the colour and width controls to highlight areas before taking a screenshot. Click Clear to remove annotations.

ℹ Captured element context is automatically pre-filled into bug report forms. If you inspect an element and then switch to the Report tab, the element field is already populated.

Features

## 🤖 AI Analysis

Every time you navigate to a new page, coTestPilot runs three analyses automatically:

Test Cases
Analyze
Likely Bugs

### Test Cases

Generates a structured, numbered test suite from the live page. Each test case includes step-by-step instructions and expected outcomes. You can run any case with one click and get an instant Pass/Fail result.

### Analyze

A broad page-level analysis covering: risk areas, missing validations, edge cases, performance concerns, accessibility issues, and UX problems. Results are grouped by severity.

### Likely Bugs

Predicts the most likely bugs before you test. The engine reads your page — its forms, interactions, data flows, and accessibility structure — and surfaces failure modes that commonly slip past manual testers. Each bug includes:

- Bug title and description
- Likelihood score (high / medium / low)
- A one-line verification hint
- Create Bug → button to pre-fill and open the bug report form

💡 All three analyses run in parallel. Results are cached per URL — switching tabs doesn't re-trigger the analysis. Click ↺ Reset in the page info bar to force a fresh run.

Features

## 🐛 Bug Reporting

Switch to the Report tab to file bugs. coTestPilot supports multiple trackers:

🔵
JIRA
Requires Base URL, email, and API token. Configure under Settings → JIRA.
⚫
GitHub Issues
Requires owner/org, repository, and a Personal Access Token with `repo` scope.
🟣
Linear
Requires API key and Team ID. Configure under Settings → Linear.
🔷
Azure DevOps
Requires organisation URL and personal access token.

### Filing a bug

1

#### Choose your tracker

Select JIRA, GitHub, Linear, Azure DevOps, or Local from the chip row at the top of the Report tab.

2

#### Fill in bug details

Enter a title and description. Use AI Write to auto-generate a structured description with Steps to Reproduce, Expected, and Actual behaviour.

3

#### Attach screenshot and URL

Screenshot and page URL are checked by default. Uncheck if you don't want them attached.

4

#### File Bug

Click File Bug. The bug is submitted directly to your tracker. A confirmation appears with a link to the created issue.

Features

## 📝 Form Assistant

The Form Assistant helps you populate forms with realistic test data quickly.

### Fill Form

Scans all visible fields on the page and fills them with coherent, realistic data — names, emails, phone numbers, dates, addresses. Triggers React/Vue/Angular change events so the page reacts correctly.

### Scan

Lists all detected form fields without filling them, so you can review what coTestPilot sees before committing.

### Suggest Data

For the currently selected element, suggests specific test values based on the field's type, label, and validation hints.

⚠ Form Assistant fills fields with test data only. It never reads, stores, or transmits any values you've already typed into form fields.

Features

## ✅ Test Cases

The Test Case section lets you run both AI-generated and manually created test cases.

### AI-generated test cases

Generated automatically from the page analysis. Each case has a title, steps, and expected outcome. Click the ▶ play button next to any case to execute it against the live page.

### Local test cases

Create your own test cases by typing a title and clicking Add. Local cases are saved per URL and persist across sessions.

### TestRail integration

If TestRail is configured, click Browse TestRail to pick a suite and select a case. Results (Pass/Fail/Skip/Blocked) are synced back to your TestRail run automatically.

### Result buttons

After running or manually checking a test, mark it as Pass, Fail, Skip, or Blocked. Results are shown inline and synced to TestRail if connected.

Configuration

## ⚙️ Settings

### AI Provider

coTestPilot supports multiple AI backends. Choose from the Settings → AI Provider section:

- Testers.AI — free trial, no key required. Powered by testers.ai cloud.
- Gemini — free API key from Google AI Studio
- OpenAI — API key from platform.openai.com
- Claude (Anthropic) — API key from console.anthropic.com
- Azure OpenAI — endpoint, key, and deployment name from your Azure Portal

### Appearance

Toggle between Dark and Light mode. Choose an accent colour from the swatch row (default: orange).

### Behavior

Toggle Auto-analyze on page load to control whether the three page analyses run automatically when you navigate. Disabling this lets you trigger analysis manually via the ↺ Reset button.

Configuration

## 🔗 Integrations

### JIRA

Go to Settings → JIRA and enter:

- Base URL — e.g. `https://yourorg.atlassian.net`
- Email — your Atlassian account email
- API Token — create at Atlassian API tokens
- Project Key — e.g. `PROJ`

Click Test Connection to verify before saving.

### GitHub Issues

Go to Settings → GitHub Issues and enter owner/org, repository name, and a Personal Access Token with `repo` scope.

### Linear

Go to Settings → Linear and enter your API key (from Linear → Settings → API) and the Team ID you want issues filed in.

### TestRail

Go to Settings → TestRail and enter your TestRail URL, email, API key, and project ID. Optionally specify a run ID to have results synced automatically.

### Google Sheets (Data Sheet)

Paste a Google Apps Script Web App URL into Settings → Data Sheet. Bug reports, test cases, and results will be logged to your sheet automatically.

Configuration

## 📋 Context Snippets

Context snippets are short text blocks injected into every AI call. Use them to give the AI knowledge about your application that isn't visible on the page — credentials, feature specs, known issues, user personas.

### Scopes

- Global — sent with every AI call, regardless of URL
- This Domain — sent only on pages matching the current domain
- This URL — sent only on the exact current URL

💡 Example: add a Global snippet with your app's login credentials so the AI can suggest test steps that include authentication. Add a URL-scoped snippet with edge-case notes for a complex form you're testing.

Configuration

## 🌐 Language

Go to Settings → Language to switch between:

- 🇬🇧 English
- 🇮🇳 हिन्दी (Hindi)
- 🇨🇳 中文 (Mandarin)
- 🇪🇸 Español (Spanish)

On first launch, coTestPilot auto-detects your browser's language setting. Once you manually select a language, your preference is saved and used on all subsequent launches.

Reference

## 💡 Tips & Tricks

### Create a bug directly from Likely Bugs

Each card in the Likely Bugs tab has a Create Bug → button. Clicking it pre-fills the bug title, description, severity, and page URL into the Report form — no manual copying.

### Use the ↺ Reset button

The Reset button clears all cached analysis and re-runs everything from scratch. Use it after making changes to the page or when you want a fresh set of suggestions.

### Auto-track toggle

The ⏸ Paused / ▶ Live button controls whether the sidebar updates when you navigate. Keep it Paused while clicking around so the sidebar doesn't reset mid-test. Switch to Live when you want automatic updates.

### Save test cases locally

Generated test cases can be saved per URL. They appear above the AI-generated list and persist across sessions, useful for regression testing the same page repeatedly.

### Reduce API rate-limit pressure

Go to Settings → API Usage → Analyses per inspect and lower the number. This runs AI analyses sequentially instead of all at once, reducing the chance of hitting rate limits on free API tiers.

### Session notes

Use the Session Notes section to jot observations, steps taken, and anything you want to remember. Notes are saved per session and can be exported as part of a report.

Reference

## ❓ FAQ

### Why isn't the sidebar updating when I navigate?

Auto-track is off by default. Click ⏸ Paused in the page info bar to switch to ▶ Live mode, or click ↺ Reset manually after navigating.

### Why are AI results in English even though I selected another language?

The language setting translates the coTestPilot UI (labels, buttons, section titles). AI-generated content (test cases, bug descriptions, analysis) is returned in whatever language your AI provider responds in. Add a context snippet telling the AI to respond in your preferred language for fully localised output.

### How do I get the Testers.AI free trial?

Go to Settings → AI Provider → Testers.AI, enter your email and an unlock code. Visit testers.ai to get a free trial code.

### Is my data sent anywhere?

Page context (URL, title, visible text) is sent to the AI API only when you trigger an analysis. Bug reports are sent to your configured tracker. Nothing is sent to coTestPilot servers. See the Privacy Policy for full details.

### How do I install from a zip file?

1. Unzip the downloaded file
2. Open `chrome://extensions` in Chrome
3. Enable Developer mode (top right toggle)
4. Click Load unpacked
5. Select the unzipped folder

### Can I use coTestPilot with my own AI key?

Yes. Go to Settings → AI Provider and select Gemini, OpenAI, Claude, or Azure. Paste your API key and choose a model. Your key is stored locally in Chrome storage and never sent to coTestPilot servers.