TestPilot AI
FeaturesSidebar UITestPilot AI adds a dedicated panel in the VS Code Activity Bar with a React-based interface:
AI ProviderTestPilot AI supports three AI back-ends, configured via
Chat Participant —
|
| Command | Description |
|---|---|
/testcases |
Generate a structured JSON list of test cases — prompts you to choose System, E2E, or Unit testing |
/selectors |
Generate Playwright CSS/XPath or WDIO accessibility-ID selectors |
/mockdata |
Generate API mock data fixtures for use in test mocking |
/codegen |
Generate automation code for a feature or component |
/heal |
Auto-detect and fix failing Playwright or WDIO tests from an error trace |
All commands except /testcases run in agent mode so Copilot can write files directly to your workspace.
Multi-Stack Support
Choose your target framework at generation time:
- Default Web — Playwright + Cucumber (TypeScript)
- Default Mobile — WDIO + Cucumber (TypeScript)
Project Scaffolding
The Setup Test Framework button detects your workspace and scaffolds a complete, production-ready framework including:
- Playwright & WDIO driver adapters
- Page Object base classes (
BaseActions,BaseSelectors,BaseIdentifiers) - Cucumber config,
tsconfig, andplaywright.config.ts - Allure reporting setup (web + mobile)
- Mobile mock server (
json-server+ step definitions) - All required
package.jsonscripts
JIRA Integration
Connect TestPilot AI to your Atlassian JIRA instance to fetch ticket details (summary, description, acceptance criteria) and use them as test generation input — no copy-pasting required. Any Confluence links within a ticket are automatically fetched and included as context.
Figma Integration
Attach a Figma API token to enrich JIRA stories with design context. When a JIRA ticket contains Figma links, TestPilot AI fetches the referenced designs and describes them using vision AI before generating test cases.
Requirements
- VS Code 1.103.0 or higher
- A TestPilot AI API key (see Getting Access below)
- GitHub Copilot Chat — required only when
test-pilot.aiExtensioniscopilot(the default)
Getting Access
TestPilot AI requires an API key tied to your work email.
- Open the sidebar — the sign-up screen appears on first launch.
- Enter your work email and click Request Access.
- You will receive an API key by slack.
- Enter the key in the Authorize step and click Authorize.
Once authorised, TestPilot AI loads and your session persists across VS Code restarts. To sign out, use the account menu in the sidebar header.
Getting Started
1. Open the Sidebar
Click the TestPilot AI icon in the VS Code Activity Bar (left sidebar) and complete the sign-up flow above.
2. Generate Test Cases
Via the sidebar:
- Select an input tab: URL, Source, Guidelines, or JIRA
- Enter your input (paste a URL, source code, acceptance criteria, or a JIRA ticket ID)
- Optionally add a related file path in the Add Related Files step
- Click 1) Test Cases — test cases appear in the output panel
Via Copilot Chat (requires copilot mode):
@test-pilot-qa /testcases <your feature spec, source code, or URL>
You will be prompted to choose a test type: System Testing, E2E Testing, or Unit Testing. Attach files with the paperclip button for additional context.
3. Review & Approve Test Cases
Generated test cases appear in the Test Cases tab. Filter by section (Functional / Non-Functional / Security), select individual rows or click Approve All, then proceed to step 4.
4. Generate Test Files
Via the sidebar: Click 4) Action, Feature & Step
Select Default Web (Playwright + Cucumber) or Default Mobile (WDIO + Cucumber) when prompted. Copilot agent will create the Actions, Feature, and Step files in your workspace.
5. Generate Selectors
@test-pilot-qa /selectors <page URL or component description>
6. Generate Mock Data
@test-pilot-qa /mockdata
Runs against the currently approved test cases.
7. Self-Heal Failing Tests
Via the sidebar:
- Paste the test error output in the Self Heal section
- Click Heal
Via Copilot Chat:
@test-pilot-qa /heal <paste your error here>
8. Set Up a New Test Project
Click Setup Test Framework in the sidebar. Select a target folder and choose Web, Mobile, or Both — TestPilot AI will scaffold the full framework and run yarn install automatically.
JIRA Configuration
Open VS Code Settings (Ctrl+, / Cmd+,) and search test-pilot:
| Setting | Description |
|---|---|
test-pilot.jiraBaseUrl |
Your Atlassian instance URL, e.g. https://yourcompany.atlassian.net |
test-pilot.jiraUsername |
Your JIRA email address |
test-pilot.jiraApiToken |
API token — generate at id.atlassian.com |
Figma Configuration
| Setting | Description |
|---|---|
test-pilot.figmaApiToken |
Personal access token from figma.com/settings — enables design enrichment for JIRA tickets that contain Figma links |
Commands
| Command | Description |
|---|---|
Open Test Pilot |
Open the TestPilot AI output panel |
Extension Settings
| Setting | Type | Default | Description |
|---|---|---|---|
test-pilot.aiExtension |
string |
"copilot" |
AI provider: copilot, claude-code, or custom |
test-pilot.jiraBaseUrl |
string |
"" |
JIRA instance base URL |
test-pilot.jiraUsername |
string |
"" |
JIRA username (email) |
test-pilot.jiraApiToken |
string |
"" |
JIRA API token |
test-pilot.figmaApiToken |
string |
"" |
Figma personal access token |
Known Issues
Please report issues on the GitHub repository.
Release Notes
0.0.2
- API key authentication — request access via email; session persists across restarts
- Multi-AI provider support — switch between Copilot, Claude Code, or custom clipboard fallback via
test-pilot.aiExtension - Figma integration — JIRA stories auto-enriched with Figma design context
- Confluence integration — linked Confluence pages automatically fetched as test generation context
- Test type picker for
/testcases— choose System Testing, E2E Testing, or Unit Testing - Improved error handling across all services with structured console logging
- Output panel now uses tabbed layout (Test Cases | JIRA)
0.0.1
Initial release:
- Sidebar UI with URL / Source / Guidelines / JIRA input tabs
- One-click generation of test cases, selectors, mock data, and test files
- Self-heal section for auto-fixing failing tests
- Output panel with test case review and JIRA detail tabs
@test-pilot-qachat participant with/testcases,/lazy-automate,/selectors,/mockdata,/codegen, and/healcommands- Multi-stack support: Playwright + Cucumber (Web) and WDIO + Cucumber (Mobile)
- Project scaffolding via Setup Test Framework button with full framework structure
- JIRA integration with configurable credentials
Enjoy testing with TestPilot AI!