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 |
|---|---|
/setup |
Scaffold the test framework in a folder you choose |
/fetch <TICKET-ID> |
Fetch a JIRA ticket and load it as test generation context |
/testcases |
Generate a structured list of test cases — prompts you to choose System, E2E, or Unit testing |
/selectors |
Generate element selectors and page-object files |
/mockdata |
Generate API mock data fixtures for use in test mocking |
/codegen |
Generate services, Cucumber feature files, and step definitions |
/loadmore [description] |
Load up to 5 additional test cases |
/heal |
Auto-detect and fix failing Playwright or WDIO tests from an error trace |
/clearall |
Clear all test cases and JIRA results |
/selectors, /mockdata, /codegen, and /heal run in agent mode so Copilot can write files directly to your workspace.
Multi-Stack Support
Choose your target framework at generation time:
- Web — Playwright + Cucumber (TypeScript)
- Mobile — WDIO + Cucumber (TypeScript)
Project scaffolding additionally offers a unified Both option that drives web and mobile from one framework.
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 company email address on an approved organisation domain (see Getting Access below)
- GitHub Copilot Chat — required only when
test-pilot.aiExtensioniscopilot(the default); use the Claude Code extension instead when set toclaude-code - Node.js via nvm — required for the scaffolded test framework (
nvm installandyarn installrun automatically during project setup)
Getting Access
TestPilot AI requires you to sign in with your company email. Authentication happens securely in your web browser — no passwords are entered inside VS Code.
- Click the TestPilot AI icon in the Activity Bar — the Sign In card appears on first launch.
- Click Continue in Browser. The hosted sign-in page opens in your default browser.
- Sign in with your existing account, or click Create an account, register with your company email, and verify it with the OTP. Sign-up is only accepted for approved organisation email domains — personal addresses (Gmail, Outlook, etc.) are rejected.
- The browser redirects back to VS Code and the sidebar unlocks.
Your session is stored securely in your operating system's credential store and persists across VS Code restarts. To sign out, run Test Pilot: Logout from the Command Palette.
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), approve individual rows or click Approve All. Buttons 2–4 in the sidebar stay disabled until at least one test case is approved.
4. Generate Selectors & Identifiers
Via the sidebar: click 2) Selectors & Identifiers and pick your stack — web (Playwright + Cucumber) or mobile (WDIO + Cucumber). The page-object files ({page}.object.ts, {page}.interface.ts, {page}.page.ts) are written into your scaffolded project.
Via Copilot Chat:
@test-pilot-qa /selectors
5. Generate Mock Data
Via the sidebar: click 3) Mock Data — JSON fixtures are generated under resources/mockdata/ for the API calls your approved test cases exercise.
Via Copilot Chat:
@test-pilot-qa /mockdata
6. Generate Service, Feature & Step Files
Via the sidebar: click 4) Service, Feature & Step and pick your stack. The agent generates services/{page}.services.ts, Cucumber features/*.feature files, and steps/*.steps.ts step definitions for your approved test cases.
Via Copilot Chat:
@test-pilot-qa /codegen
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 |
|---|---|
Test Pilot: Open Webview |
Open the TestPilot AI output panel |
Test Pilot: Logout |
Sign out and remove the stored session |
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 |
Enjoy testing with TestPilot AI!