@testdriverai/mcp 7.9.149-test → 7.9.151-test

package/ai/skills/testdriver-quickstart/SKILL.md

@@ -9,6 +9,53 @@ TestDriver makes it easy to write automated computer-use tests for web browsers,
 <Tip><a href="https://discord.com/invite/cWDFW8DzPm" target="_blank" rel="noreferrer">Join our Discord</a> if you have any questions or need help getting started!</Tip>
 
 <Tabs>
+  <Tab title="Add to GitHub" icon="github">
+
+    Drop-in UI testing for any GitHub repository. Mention `@testdriverai` anywhere in your repo and it writes UI tests and catches regressions before they merge.
+
+    <Card
+      title="Add to GitHub"
+      icon="github"
+      href="https://go.testdriver.ai/github"
+      arrow
+      horizontal
+    >
+      Install the TestDriver GitHub app and start testing in minutes — no setup required.
+    </Card>
+
+    <Steps>
+      <Step title="Install the GitHub App">
+        Click **Add to GitHub** above and install TestDriver on the repositories you want to test.
+      </Step>
+
+      <Step title="Mention @testdriverai">
+        Open a pull request or issue and mention `@testdriverai` to have it write and run UI tests:
+
+        ```
+        @testdriverai Write a test that verifies the homepage loads and the signup button works.
+        ```
+
+        TestDriver spawns a sandbox, writes the test, and posts results right in the conversation.
+      </Step>
+
+      <Step title="Catch Regressions Automatically">
+        Once your tests are committed, TestDriver runs them on every pull request and flags regressions before they merge.
+      </Step>
+    </Steps>
+
+    Want to use TestDriver from GitHub Copilot or the GitHub Mobile app instead? See the full GitHub guide:
+
+    <Card
+      title="GitHub Integration Guide"
+      icon="arrow-right"
+      href="/v7/copilot/auto-healing#use-testdriver-in-github"
+      arrow
+      horizontal
+    >
+      Use TestDriver from GitHub web, Copilot chat, PR reviews, and mobile.
+    </Card>
+
+  </Tab>
   <Tab title="CLI" icon="terminal">
 
     Get started quickly with the TestDriver CLI.
@@ -39,34 +86,6 @@ TestDriver makes it easy to write automated computer-use tests for web browsers,
       </Step>
     </Steps>
   </Tab>
-  <Tab title="GitHub Copilot" icon="github">
-
-    Use the TestDriver VS Code extension with GitHub Copilot for an AI-powered testing workflow.
-
-    <Card
-      title="Install TestDriver for VS Code"
-      icon="/images/content/extension/vscode.svg"
-      href="vscode:extension/testdriver.testdriver"
-      arrow
-      horizontal
-    >
-    </Card>
-
-    The extension provides one-click sign-in, project initialization, a live preview panel for watching tests execute, and MCP server configuration for GitHub Copilot.
-
-    Once installed, follow the full setup guide to configure MCP and start building tests with AI assistance:
-
-    <Card
-      title="VS Code + Copilot Setup Guide"
-      icon="arrow-right"
-      href="/v7/copilot/setup"
-      arrow
-      horizontal
-    >
-      Sign in, initialize your project, and configure MCP for GitHub Copilot.
-    </Card>
-
-  </Tab>
   <Tab title="Manual" icon="wrench">
 
     Install TestDriver and manually create the files yourself.

package/ai/skills/testdriver-wait/SKILL.md

@@ -47,4 +47,4 @@ await testdriver.wait();
   const element = await testdriver.find('success message');
   ```
 - Avoid excessively long timeouts to keep tests efficient.
-- Use sparingly — TestDriver's [redraw detection](/v7/waiting-for-elements) automatically waits for screen and network stability after each action.
+- Use sparingly — TestDriver's [redraw detection](/v7/performing-actions#waiting-for-dynamic-content) automatically waits for screen and network stability after each action.

package/ai/skills/testdriver:generating-tests/SKILL.md

@@ -23,14 +23,3 @@ Type password Password123 into Password field
 Push Submit button
 Verify new page contains expected text 'logged in'
 ```
-
-## AI Exploration Mode
-
-Within a test, the `ai()` method lets TestDriver autonomously figure out how to accomplish a task. It's useful for dynamic or unpredictable UIs where explicit actions may be difficult to define.
-
-```javascript
-// Handle dynamic or unpredictable UI
-await testdriver.ai('dismiss any popups or modals that appear');
-```
-
-<Info>Explicit commands are preferred for production tests, as they are cheaper, faster, and more reliable.</Info>

package/docs/changelog.mdx

@@ -93,7 +93,7 @@ This release includes all changes from v7.8.0-test.6 with version bumps across a
 
 ✨ New features
 
-- **[GitHub Copilot integration](/v7/copilot/setup)** — Use TestDriver directly from GitHub Copilot in VS Code. The new MCP server lets Copilot launch sandboxes, interact with elements, and run assertions through natural language. Includes guides for [creating tests](/v7/copilot/creating-tests), [running tests](/v7/copilot/running-tests), [GitHub Actions integration](/v7/copilot/github), and [auto-healing](/v7/copilot/auto-healing).
+- **[GitHub Copilot integration](/v7/copilot/running-tests)** — Use TestDriver directly from GitHub Copilot in VS Code. The new MCP server lets Copilot launch sandboxes, interact with elements, and run assertions through natural language. Includes guides for [creating tests](/v7/generating-tests), [running tests](/v7/copilot/running-tests), [GitHub Actions integration](/v7/copilot/auto-healing#use-testdriver-in-github), and [auto-healing](/v7/copilot/auto-healing).
 
 🔧 Improvements
 

package/docs/docs.json

@@ -53,33 +53,16 @@
               "/changelog"
             ]
           },
-          {
-            "group": "GitHub Copilot",
-            "pages": [
-              "/v7/copilot/setup",
-              "/v7/copilot/creating-tests",
-              "/v7/copilot/running-tests",
-              "/v7/copilot/github",
-              "/v7/copilot/auto-healing"
-            ]
-          },
           {
             "group": "Guide",
             "pages": [
               "/v7/generating-tests",
-              "/v7/device-config",
-              "/v7/machine-setup",
-              "/v7/locating-elements",
-              "/v7/waiting-for-elements",
-              "/v7/performing-actions",
-              "/v7/making-assertions"
-            ]
-          },
-          {
-            "group": "Running Tests",
-            "pages": [
-              "/v7/running-tests",
               "/v7/caching",
+              "/v7/copilot/running-tests",
+              "/v7/making-assertions",
+              "/v7/performing-actions",
+              "/v7/debugging-with-screenshots",
+              "/v7/copilot/auto-healing",
               "/v7/ci-cd",
               "/v7/test-results-json"
             ]
@@ -91,7 +74,7 @@
               "/v7/secrets",
               "/v7/reusable-code",
               {
-                "group": "Self-Hosting Setup",
+                "group": "Self-Hosting",
                 "icon": "server",
                 "pages": [
                   "/v7/aws-setup"
@@ -99,25 +82,9 @@
               }
             ]
           },
-          {
-            "group": "AI",
-            "icon": "robot",
-            "pages": [
-              "/v7/ai/agent",
-              "/v7/ai/skills",
-              "/v7/ai/mcp"
-            ]
-          },
           {
             "group": "Actions",
             "pages": [
-              {
-                "group": "ai",
-                "tag": "Beta",
-                "pages": [
-                  "/v7/ai"
-                ]
-              },
               "/v7/assert",
               "/v7/captcha",
               "/v7/click",
@@ -366,6 +333,14 @@
     }
   },
   "redirects": [
+    {
+      "source": "/v7/ai",
+      "destination": "/v7/quickstart"
+    },
+    {
+      "source": "/v7/ai/:slug*",
+      "destination": "/v7/quickstart"
+    },
     {
       "source": "/guides/github-actions",
       "destination": "/v6/action/setup"

package/docs/v7/assert.mdx

@@ -313,4 +313,3 @@ describe('Assertions', () => {
 
 - [`extract()`](/v7/extract) - Extract information for detailed assertions
 - [`find()`](/v7/find) - Locate elements to verify
-- [`ai()`](/v7/ai) - Complex AI-driven tasks

package/docs/v7/caching.mdx

@@ -1,11 +1,13 @@
 ---
-title: "Caching Prompts"
-description: "1.7x faster test execution with intelligent caching and optimization"
-icon: "bolt"
+title: "Learn"
+sidebarTitle: "Learn"
+description: "How TestDriver learns your app and caches what it discovers for instant, deterministic replays"
+icon: "brain"
 ---
 
-TestDriver is engineered for performance with intelligent caching that delivers up to **1.7x faster** test execution by skipping redundant AI vision analysis.
+Once the agent has [explored your app](/v7/generating-tests), TestDriver remembers what it found. Every element the AI vision agent discovers is cached with a vision fingerprint—a perceptual hash of the screen state where it was located. On the next run, TestDriver matches against that cache instead of calling the AI again. Passing tests replay instantly, deterministically, and cheaply.
 
+This learning is what makes TestDriver fast. Intelligent caching delivers up to **1.7x faster** test execution by skipping redundant AI vision analysis—the agent only thinks when it sees something new.
 
 ```javascript
 // First run: builds cache
@@ -17,7 +19,7 @@ await testdriver.find('submit button');
 
 ## Automatic Caching
 
-Caching is enabled automatically with zero configuration. The cache key is computed from:
+Learning is enabled automatically with zero configuration. The cache key—the fingerprint TestDriver uses to recognize what it already knows—is computed from:
 
 - **File hash**: SHA-256 hash of the test file contents
 - **Selector prompt**: The exact text description passed to `find()`
@@ -53,7 +55,7 @@ You can clear the cache within the TestDriver console. There, you'll also find p
 
 ## Debugging Cache Hits and Misses
 
-You can track cache performance in your tests:
+You can track what TestDriver has learned by inspecting cache performance in your tests:
 
 ```javascript
 test('monitor cache performance', async (context) => {
@@ -75,7 +77,7 @@ test('monitor cache performance', async (context) => {
 
 ## Configuring the Cache
 
-You can configure cache behavior globally when initializing TestDriver:
+You can configure how TestDriver learns globally when initializing TestDriver:
 
 ```javascript
 import { TestDriver } from 'testdriverai';
@@ -103,7 +105,7 @@ await testdriver.find('submit button', {
 
 ## Caching with Variables
 
-Custom cache keys prevent cache pollution when using variables in prompts, dramatically improving cache hit rates.
+Custom cache keys prevent cache pollution when using variables in prompts, dramatically improving cache hit rates—so TestDriver reuses what it learned even when your data changes.
 
 ```javascript
 // ❌ Without cache key - creates new cache for each variable value
@@ -123,6 +125,8 @@ await testdriver.find(`order ${orderId} status`, {
 });
 ```
 
+## Next
 
-
-
+<Card href="/v7/copilot/running-tests" title="Run" icon="play">
+  Now that TestDriver has learned your app, run your tests in CI and locally—replaying the cache for fast, deterministic results.
+</Card>

package/docs/v7/client.mdx

@@ -54,7 +54,7 @@ const testdriver = new TestDriver(apiKey, options)
     </ParamField>
     
     <ParamField path="reconnect" type="boolean" default="false">
-      Reattach to the last used sandbox instead of creating a new one. When `true`, the SDK reads the sandbox id from `.testdriver/last-sandbox` (written automatically on every successful connect) and rejoins that VM. Provision methods (`chrome`, `vscode`, `installer`, etc.) are skipped because the application is already running. The previous sandbox must still be alive — see [`keepAlive`](#keepalive) and the [Machine Setup guide](/v7/machine-setup#keeping-machines-alive-between-runs).
+      Reattach to the last used sandbox instead of creating a new one. When `true`, the SDK reads the sandbox id from `.testdriver/last-sandbox` (written automatically on every successful connect) and rejoins that VM. Provision methods (`chrome`, `vscode`, `installer`, etc.) are skipped because the application is already running. The previous sandbox must still be alive — see [`keepAlive`](#keepalive) and the [Run guide](/v7/copilot/running-tests#keeping-machines-alive-between-runs).
     </ParamField>
 
     <ParamField path="sandboxId" type="string">

package/docs/v7/copilot/auto-healing.mdx

@@ -1,23 +1,168 @@
 ---
-title: "Auto-Healing Tests"
-sidebarTitle: "Auto-Healing"
-description: "Set up automatic test repair in CI using GitHub Copilot and TestDriver"
-icon: "bandage"
+title: "Prevent"
+sidebarTitle: "Prevent"
+description: "Catch regressions automatically with CI, auto-healing, and GitHub integration"
+icon: "shield-check"
 ---
 
-Auto-healing tests automatically fix themselves when your application changes. By integrating GitHub Copilot with TestDriver in your CI pipeline, you can have AI investigate test failures and propose fixes.
+Prevent regressions by letting TestDriver run and repair itself on every change. Once you've [explored](/v7/generating-tests), [taught it your app](/v7/caching), [run it](/v7/copilot/running-tests), [validated outcomes](/v7/making-assertions), [adapted to your UI](/v7/performing-actions), and learned to [debug with screenshots](/v7/debugging-with-screenshots), the last step is closing the loop: wire TestDriver into your pull requests so regressions never reach production.
 
-## How It Works
+Your AI agent can run tests on every PR, investigate failures, and propose fixes — and you can drive all of it from GitHub itself, whether you're at your desk or on your phone.
+
+## Use TestDriver in GitHub
+
+TestDriver works directly in GitHub's web interface and mobile app. The same MCP server that powers VS Code integration also works in GitHub, letting you create and manage tests from anywhere.
+
+### How It Works
+
+When you add a TestDriver agent file to your repository at `.github/agents/testdriver.agent.md`, GitHub Copilot can use TestDriver's MCP tools directly in:
+
+- GitHub.com (web browser)
+- GitHub Mobile app (iOS/Android)
+- Pull request conversations
+- Issue comments
+
+### Using TestDriver in GitHub Web
+
+<Steps>
+  <Step title="Navigate to Your Repository">
+    Open your repository on GitHub.com. Make sure you have the TestDriver agent file at `.github/agents/testdriver.agent.md`.
+  </Step>
+
+  <Step title="Start a Copilot Chat">
+    Click the **Copilot icon** in the GitHub interface to open a chat. You can find this in:
+    - The repository's Code tab
+    - Pull request pages
+    - Issue pages
+  </Step>
+
+  <Step title="Invoke the TestDriver Agent">
+    Start your message with `@testdriver`:
+
+    ```
+    @testdriver Create a test that verifies the homepage loads correctly at https://myapp.com
+    ```
+
+    The agent will spawn a sandbox environment and begin executing, just like in VS Code.
+  </Step>
+
+  <Step title="View Screenshots in Chat">
+    As the test runs, screenshots appear directly in the chat. You can see what the AI sees and provide guidance if needed.
+  </Step>
+</Steps>
+
+### Creating Tests from PR Comments
+
+You can create tests directly from pull request reviews. Comment on a PR and mention Copilot:
+
+```
+@copilot create a TestDriver test that verifies this new feature works.
+Test the checkout flow with a guest user.
+```
+
+Copilot will:
+1. Use the TestDriver MCP server
+2. Create a test based on your description
+3. Commit the test file to the PR branch
+
+This is useful for:
+- Adding test coverage during code review
+- Verifying bug fixes before merging
+- Creating regression tests for new features
+
+### Creating Tests from Issues
+
+You can also create tests from issue comments:
+
+```
+@copilot Use TestDriver to create a test that reproduces this bug.
+Navigate to /settings, change the theme, and verify it persists after refresh.
+```
+
+The test will be created in a new branch and linked to the issue.
+
+### Mobile App Support
+
+The GitHub Mobile app supports Copilot chat, which means you can use TestDriver from your phone:
+
+1. Open the GitHub app
+2. Navigate to your repository
+3. Tap the Copilot icon
+4. Type `@testdriver` followed by your request
+
+Screenshots and test progress appear in the chat, letting you create and debug tests on the go.
+
+### Example: PR Review Workflow
+
+Here's a complete workflow for adding tests during code review:
+
+<Steps>
+  <Step title="Developer Opens PR">
+    A developer opens a pull request with a new feature.
+  </Step>
+
+  <Step title="Reviewer Requests Tests">
+    The reviewer comments:
+    ```
+    @copilot Create a TestDriver test for this user registration flow.
+    Test both successful registration and validation errors.
+    ```
+  </Step>
+
+  <Step title="Copilot Creates Tests">
+    Copilot spawns TestDriver, creates the tests, and commits them to the PR branch.
+  </Step>
+
+  <Step title="Tests Run in CI">
+    The new tests run automatically in CI, validating the feature works as expected.
+  </Step>
+</Steps>
+
+### Agent File Reference
+
+The agent file at `.github/agents/testdriver.agent.md` contains the configuration for GitHub Copilot to use TestDriver. Here's the structure:
+
+```yaml
+---
+name: testdriver
+description: An expert at creating and refining automated tests using TestDriver.ai
+mcp-servers:
+  testdriver:
+    command: npx
+    args:
+      - -p
+      - testdriverai
+      - testdriverai-mcp
+    env:
+      TD_API_KEY: ${TD_API_KEY}
+---
+
+# TestDriver Expert
+
+You are an expert at writing automated tests using TestDriver...
+```
+
+The `TD_API_KEY` is pulled from your repository secrets when running in GitHub Actions or from your environment when using the web interface.
+
+<Warning>
+  Make sure `TD_API_KEY` is set in your repository secrets for CI workflows. Go to **Settings → Secrets and variables → Actions** to add it.
+</Warning>
+
+## Auto-Healing Tests
+
+Auto-healing tests automatically fix themselves when your application changes. By integrating an AI coding agent with TestDriver in your CI pipeline, you can have AI investigate test failures and propose fixes. The example below uses GitHub Copilot in GitHub Actions, but the same approach works with any AI agent that can run TestDriver's MCP server.
+
+### How It Works
 
 When a test fails in CI:
 
 1. **GitHub Actions detects the failure**
-2. **Copilot spawns the TestDriver agent** with access to the MCP server
+2. **The AI agent spawns TestDriver** with access to the MCP server
 3. **The agent investigates** by running the failing test and analyzing what changed
-4. **Copilot creates a fix** by updating the test code
+4. **The agent creates a fix** by updating the test code
 5. **A pull request is opened** with the proposed changes for review
 
-## Setting Up Auto-Healing
+### Setting Up Auto-Healing
 
 <Steps>
   <Step title="Add Repository Secrets">
@@ -131,7 +276,7 @@ When a test fails in CI:
   </Step>
 </Steps>
 
-## Example: Button Text Change
+### Example: Button Text Change
 
 Here's what auto-healing looks like when a button's text changes:
 
@@ -158,7 +303,7 @@ Here's what auto-healing looks like when a button's text changes:
   </Step>
 
   <Step title="Auto-Heal Triggers">
-    The auto-heal workflow runs, and Copilot investigates:
+    The auto-heal workflow runs, and the AI agent investigates:
 
     ```
     The test is looking for a "Submit button" but I see a "Send button"
@@ -177,9 +322,9 @@ Here's what auto-healing looks like when a button's text changes:
   </Step>
 </Steps>
 
-## Configuration Options
+### Configuration Options
 
-### Selective Auto-Healing
+#### Selective Auto-Healing
 
 You can limit auto-healing to specific test files or patterns:
 
@@ -190,7 +335,7 @@ You can limit auto-healing to specific test files or patterns:
     vitest run tests/e2e/ 2>&1 | tee test-output.txt
 ```
 
-### Manual Approval
+#### Manual Approval
 
 For safety, you can require manual approval before auto-heal runs:
 
@@ -202,7 +347,7 @@ jobs:
 
 Configure the environment in **Settings → Environments** with required reviewers.
 
-### Limiting Changes
+#### Limiting Changes
 
 Add instructions to constrain what the AI can change:
 
@@ -220,7 +365,7 @@ Add instructions to constrain what the AI can change:
       - Keep changes minimal
 ```
 
-## Best Practices
+### Best Practices
 
 <AccordionGroup>
   <Accordion title="Always review auto-heal PRs">
@@ -250,7 +395,7 @@ Add instructions to constrain what the AI can change:
   </Accordion>
 </AccordionGroup>
 
-## Limitations
+### Limitations
 
 Auto-healing works best for:
 - Element text changes
@@ -262,4 +407,8 @@ It may struggle with:
 - New features requiring new assertions
 - Complex multi-step interactions
 
-For significant changes, create new tests manually using the [TestDriver agent](/v7/copilot/creating-tests).
+For significant changes, create new tests by going back to [Explore](/v7/generating-tests) and generating them with the TestDriver agent.
+
+<Card title="View Your Runs" icon="chart-line" href="https://console.testdriver.ai">
+  Open the TestDriver console to monitor test runs, healing PRs, and CI results across your projects.
+</Card>