@testdriverai/mcp 7.11.136-test → 7.11.138-test

package/docs/{v7/reusable-code.mdx → reusable-code.mdx}

@@ -4,11 +4,11 @@ description: "Build maintainable test suites with reusable code patterns"
 icon: "recycle"
 ---
 
-As your test suite grows, you'll want to extract common patterns into reusable code. This keeps tests DRY, readable, and easy to maintain.
+When your test suite becomes larger, put the common patterns into reusable code. This keeps the tests short, easy to read, and easy to keep.
 
 ## Helper Functions
 
-The simplest approach is extracting common actions into helper functions. Create a `helpers/` directory for shared utilities:
+The most simple method is to put the common actions into helper functions. Make a `helpers/` directory for the shared utilities:
 
 ```javascript test/helpers/auth.js
 export async function login(testdriver, { email, password }) {
@@ -37,7 +37,7 @@ export async function logout(testdriver) {
 ```
 
 <Warning>
-**Avoid hardcoding dynamic values in element descriptions.** Element selectors should describe the *type* of element, not specific content that might change.
+**Do not put dynamic values in element descriptions.** An element selector must describe the *type* of the element. It must not describe specific content that can change.
 
 **❌ Bad:** `await testdriver.find('profile name TestDriver in the top right')`  
 **✅ Good:** `await testdriver.find('user profile name in the top right')`

package/docs/{v7/right-click.mdx → right-click.mdx}

@@ -6,7 +6,7 @@ icon: "bars"
 
 ## Overview
 
-The `rightClick()` method performs a right-click action on an element, typically used to open context menus. You can either call it on an [`Element`](/v7/core-concepts/elements) instance or use it directly with a selector.
+The `rightClick()` method does a right-click action on an element. It usually opens context menus. You can call it on an [`Element`](/core-concepts/elements) instance. Or you can use it with a selector.
 
 ## Syntax
 
@@ -30,7 +30,7 @@ When called directly on the AI client:
 
 ## Returns
 
-Returns a `Promise<void>` that resolves when the right-click action completes.
+It returns a `Promise<void>`. The promise resolves when the right-click action completes.
 
 ## Examples
 
@@ -116,8 +116,8 @@ test('uses custom context menu', async () => {
 
 ## Related Methods
 
-- [`click()`](/v7/click) - Single click on an element
-- [`doubleClick()`](/v7/double-click) - Double-click on an element
-- [`mouseDown()`](/v7/mouse-down) - Press mouse button without releasing
-- [`mouseUp()`](/v7/mouse-up) - Release mouse button
-- [`hover()`](/v7/hover) - Move mouse over element without clicking
+- [`click()`](/click) - Single click on an element
+- [`doubleClick()`](/double-click) - Double-click on an element
+- [`mouseDown()`](/mouse-down) - Press mouse button without releasing
+- [`mouseUp()`](/mouse-up) - Release mouse button
+- [`hover()`](/hover) - Move mouse over element without clicking

package/docs/{v7/screenshot.mdx → screenshot.mdx}

@@ -7,10 +7,10 @@ icon: "camera"
 
 ## Overview
 
-Capture a screenshot of the current screen and automatically save it to a local file. Screenshots are organized by test file for easy debugging and review.
+Capture a screenshot of the screen. TestDriver saves it to a local file automatically. TestDriver groups the screenshots by test file. This makes debug and review easy.
 
 <Note>
-  **Automatic Screenshots**: TestDriver can automatically capture screenshots before and after every command (click, type, find, etc.). These are saved with descriptive filenames like `001-click-before-L42-submit-button.png` that include the line number from your test file. Enable this with `autoScreenshots: true` in your TestDriver options.
+  **Automatic Screenshots**: TestDriver can capture screenshots automatically before and after each command (click, type, find, and more). It saves them with clear filenames such as `001-click-before-L42-submit-button.png`. The filename includes the line number from your test file. Enable this with `autoScreenshots: true` in your TestDriver options.
 </Note>
 
 ## Syntax
@@ -22,16 +22,16 @@ const filePath = await testdriver.screenshot(filename)
 ## Parameters
 
 <ParamField path="filename" type="string" optional>
-  Custom filename for the screenshot (without .png extension). If not provided, a timestamp-based filename is generated automatically.
+  A custom filename for the screenshot (without the .png extension). If you do not give one, TestDriver makes a filename from the timestamp automatically.
 </ParamField>
 
 ## Returns
 
-`Promise<string>` - The absolute file path where the screenshot was saved
+`Promise<string>` - The absolute file path where TestDriver saved the screenshot
 
 ## File Organization
 
-Screenshots are automatically saved to `.testdriver/screenshots/<test-file-name>/` in your project root:
+TestDriver saves screenshots automatically to `.testdriver/screenshots/<test-file-name>/` in your project root:
 
 ```
 .testdriver/
@@ -239,11 +239,11 @@ These commands allow you to:
 - Compare screenshots across test runs to identify flaky behavior
 
 <Note>
-  For detailed workflows and examples of using these MCP commands for debugging, see the [Debugging with Screenshots](/v7/debugging-with-screenshots) guide.
+  For detailed workflows and examples of using these MCP commands for debugging, see the [Debugging with Screenshots](/debugging-with-screenshots) guide.
 </Note>
 
 ## Related
 
-- [Debugging with Screenshots](/v7/debugging-with-screenshots) - View and analyze saved screenshots using MCP
-- [assert()](/v7/assert) - Make AI-powered assertions
-- [find()](/v7/find) - Locate elements on screen
+- [Debugging with Screenshots](/debugging-with-screenshots) - View and analyze saved screenshots using MCP
+- [assert()](/assert) - Make AI-powered assertions
+- [find()](/find) - Locate elements on screen

package/docs/{v7/screenshots.mdx → screenshots.mdx}

@@ -8,11 +8,11 @@ mode: "wide"
 
 ## Overview
 
-TestDriver can capture screenshots manually at any point during a test, or automatically before and after every command. Screenshots are saved to a structured directory for easy debugging.
+TestDriver can capture screenshots by hand at any point during a test. It can also capture them automatically before and after each command. TestDriver saves the screenshots to a structured directory. This makes debug easy.
 
 ## Manual Screenshots
 
-Use `testdriver.screenshot()` to capture the current screen:
+Use `testdriver.screenshot()` to capture the present screen:
 
 ```javascript
 const path = await testdriver.screenshot();
@@ -27,7 +27,7 @@ await testdriver.screenshot(filename?)
 ```
 
 <ParamField path="filename" type="string">
-  Custom filename for the screenshot. `.png` is appended automatically if missing. If omitted, defaults to `screenshot-<timestamp>.png`.
+  A custom filename for the screenshot. TestDriver adds `.png` automatically if it is not there. If you do not give this, the default is `screenshot-<timestamp>.png`.
 </ParamField>
 
 **Returns:** `Promise<string>` — the absolute file path of the saved screenshot.

package/docs/{v7/scroll.mdx → scroll.mdx}

@@ -7,17 +7,17 @@ icon: "arrows-up-down"
 
 ## Overview
 
-Scroll the page or active element in any direction using mouse wheel or keyboard.
+Scroll the page or the active element in any direction with the mouse wheel or the keyboard.
 
 <Warning>
   **Focus Requirements**
   
-  Scrolling requires the page or a frame to be focused. If an input field or other interactive element has focus, scroll commands may not work as expected. Before scrolling, ensure focus is on the page by:
-  - Clicking on a non-interactive area (e.g., page background)
-  - Pressing the Escape key to unfocus interactive elements
-  - Clicking outside of input fields or text areas
+  A scroll needs focus on the page or on a frame. If an input field or another interactive element has focus, scroll commands can fail. Before you scroll, put the focus on the page:
+  - Click a non-interactive area (for example, the page background)
+  - Push the Escape key to remove the focus from interactive elements
+  - Click outside of input fields or text areas
   
-  **If scroll is still not working**, try using Page Down/Page Up keys directly:
+  **If the scroll still does not work**, use the Page Down or Page Up keys directly:
   ```javascript
   await testdriver.pressKeys(['pagedown']); // Scroll down
   await testdriver.pressKeys(['pageup']);   // Scroll up
@@ -89,7 +89,7 @@ await testdriver.pressKeys(['pagedown']);
 ## Best Practices
 
 <Check>
-  **Ensure page has focus before scrolling**
+  **Make sure that the page has focus before you scroll**
   
   ```javascript
   // After typing in an input, unfocus it first
@@ -110,7 +110,7 @@ await testdriver.pressKeys(['pagedown']);
 </Check>
 
 <Check>
-  **Control scroll distance with the options object**
+  **Control the scroll distance with the options object**
   
   ```javascript
   // For web pages, mouse scroll works well
@@ -122,9 +122,9 @@ await testdriver.pressKeys(['pagedown']);
 </Check>
 
 <Warning>
-  **Keyboard scroll uses Page Down/Up**
+  **The keyboard scroll uses Page Down and Page Up**
   
-  Keyboard scrolling typically moves by one "page" at a time, which may be more than the specified click amount. It's more compatible but less precise than mouse scrolling.
+  A keyboard scroll usually moves one "page" each time. This can be more than the click amount that you set. It is more compatible than a mouse scroll, but it is less precise.
 </Warning>
 
 ## Use Cases
@@ -201,6 +201,6 @@ describe('Scrolling', () => {
 
 ## Related Methods
 
-- [`find()`](/v7/find) - Locate elements after scrolling
-- [`pressKeys()`](/v7/press-keys) - Use Page Down/Up keys
-- [`wait()`](/v7/wait) - Wait after scrolling
+- [`find()`](/find) - Find elements after a scroll
+- [`pressKeys()`](/press-keys) - Use the Page Down and Page Up keys
+- [`wait()`](/wait) - Wait after a scroll

package/docs/{v7/secrets.mdx → secrets.mdx}

@@ -4,11 +4,11 @@ description: "Securely manage passwords and sensitive data in your tests"
 icon: "key"
 ---
 
-Protect sensitive information like passwords, API keys, and tokens in your TestDriver tests.
+Protect sensitive information such as passwords, API keys, and tokens in your TestDriver tests.
 
 ## Typing Secrets Securely
 
-When typing sensitive information like passwords, use the `secret: true` option to prevent the value from being logged or stored:
+When you type sensitive information such as passwords, use the `secret: true` option. This stops TestDriver from a log or a store of the value:
 
 ```javascript
 import { test } from 'vitest';
@@ -32,12 +32,12 @@ test('login with secure password', async (context) => {
 ```
 
 <Note>
-When `secret: true` is set, the typed text appears as `****` in all logs, recordings, and dashcam output.
+When you set `secret: true`, the typed text shows as `****` in all logs, recordings, and dashcam output.
 </Note>
 
 ## Storing Secrets in GitHub
 
-Store sensitive credentials as GitHub repository secrets so they're never exposed in your code:
+Store sensitive credentials as GitHub repository secrets. Then they are never in your code:
 
 <Steps>
   <Step title="Navigate to Repository Settings">

package/docs/{v7/self-hosted.mdx → self-hosted.mdx}

@@ -6,26 +6,26 @@ icon: "server"
 mode: "wide"
 ---
 
-Self-hosted is our enterprise solution for teams that need unlimited test execution, infrastructure control, and dedicated support. Pricing is based on **parallel test capacity** with a flat license fee — no per-second billing.
+Self-hosted is our enterprise solution. Use it for teams that need unlimited test runs, infrastructure control, and dedicated support. The price uses **parallel test capacity** with a flat license fee. There is no per-second bill.
 
 <CardGroup cols={2}>
   <Card title="Unlimited Execution" icon="infinity">
-    Run as many tests as you want with no device-second metering. Predictable monthly costs.
+    Run as many tests as you want. There is no device-second count. The monthly costs are known.
   </Card>
   <Card title="Assisted Setup & Support" icon="headset">
-    Our team helps you deploy, configure, and optimize your infrastructure. Dedicated engineering support included.
+    Our team helps you to deploy, configure, and optimize your infrastructure. Dedicated engineering support is included.
   </Card>
   <Card title="Full Control" icon="gear">
-    Use your own AI keys, custom hardware, specific software, and network configurations. RDP into test machines for debugging.
+    Use your own AI keys, custom hardware, specific software, and network configurations. Use RDP into the test machines for debug.
   </Card>
   <Card title="Security & Compliance" icon="shield-check">
-    Keep data in your environment. Air-gapped deployment available for regulated industries.
+    Keep the data in your environment. Air-gapped deployment is available for regulated industries.
   </Card>
 </CardGroup>
 
 ## Deployment Options
 
-Choose the level of control you need:
+Select the level of control that you need:
 
 | Component | Standard | Air-Gapped |
 |-----------|----------|------------|
@@ -49,7 +49,7 @@ Run test sandboxes on your AWS infrastructure while using TestDriver's hosted da
 <Card
   title="AWS Setup Guide"
   icon="aws"
-  href="/v7/aws-setup"
+  href="/aws-setup"
 >
   Step-by-step instructions for deploying TestDriver on your AWS infrastructure using CloudFormation.
 </Card>

package/docs/{v7/test-results-json.mdx → test-results-json.mdx}

@@ -7,9 +7,9 @@ icon: "file-code"
 
 ## Overview
 
-TestDriver automatically writes a JSON result file for each test case after it finishes. These files contain comprehensive metadata about the test run, including SDK and runner versions, infrastructure details, interaction statistics, and links to recordings.
+TestDriver writes a JSON result file for each test case after it finishes. These files have full metadata about the test run. This includes the SDK version, the runner version, infrastructure details, interaction statistics, and links to recordings.
 
-Result files are written to:
+TestDriver writes the result files to:
 
 ```
 .testdriver/results/<testFile>/<testName>.json
@@ -22,12 +22,12 @@ For example, a test file `tests/login.test.mjs` with a test named `"should log i
 ```
 
 <Note>
-  Test names are sanitized for filesystem use — special characters are replaced with underscores and names are truncated to 200 characters.
+  TestDriver makes the test names safe for the file system. It changes special characters to underscores. It cuts the names to 200 characters.
 </Note>
 
 ## Enabling
 
-No configuration is required. The JSON files are written automatically by the TestDriver Vitest reporter plugin whenever tests run.
+You do not need configuration. The TestDriver Vitest reporter plugin writes the JSON files automatically each time the tests run.
 
 ## JSON Schema
 

package/docs/{v7/type.mdx → type.mdx}

@@ -7,7 +7,7 @@ icon: "keyboard"
 
 ## Overview
 
-Type text or numbers into the currently focused input field with optional delay between keystrokes.
+Type text or numbers into the input field that has focus. You can set an optional delay between the keystrokes.
 
 ## Syntax
 
@@ -30,7 +30,7 @@ await testdriver.type(text, options)
     </ParamField>
     
     <ParamField path="secret" type="boolean" default={false}>
-      If `true`, treats text as sensitive data (won't be logged or stored in debug info/dashcam)
+      If `true`, TestDriver makes the text sensitive data. It does not log or store it in the debug info or in dashcam.
     </ParamField>
   </Expandable>
 </ParamField>
@@ -79,9 +79,9 @@ await testdriver.type('4111111111111111', { secret: true });
 ```
 
 <Warning>
-  **Always use `secret: true` for passwords and sensitive data!**
+  **Always use `secret: true` for passwords and sensitive data.**
   
-  Without this option, typed text appears in:
+  If you do not use this option, the typed text shows in these:
   - Dashcam video replays
   - TestDriver logs
   - Debug screenshots
@@ -353,6 +353,6 @@ describe('Form Filling with Type', () => {
 
 ## Related Methods
 
-- [`pressKeys()`](/v7/press-keys) - Press keyboard keys and shortcuts
-- [`find()`](/v7/find) - Locate input fields
-- [`click()`](/v7/click) - Focus input fields
+- [`pressKeys()`](/press-keys) - Press keyboard keys and shortcuts
+- [`find()`](/find) - Locate input fields
+- [`click()`](/click) - Focus input fields

package/docs/{v7/variables.mdx → variables.mdx}

@@ -4,11 +4,11 @@ description: "Use dynamic data and secure secrets in your tests"
 icon: "square-root-variable"
 ---
 
-Scale your testing with dynamic data and secure secrets management. Choose the right approach based on your testing needs.
+Make your tests larger with dynamic data and secure secrets. Select the correct method for your test needs.
 
 ## Environment Variables
 
-Environment variables are ideal for **configuration that changes between environments** (dev, staging, production) or for **secrets that shouldn't be committed to code**. Use this approach when you need to run the same tests against different servers or with different credentials.
+Use environment variables for **configuration that changes between environments** (dev, staging, production). Also use them for **secrets that you must not commit to the code**. Use this method when you must run the same tests against different servers or with different credentials.
 
 ```javascript
 import { test } from 'vitest';

package/docs/{v7/wait.mdx → wait.mdx}

@@ -8,7 +8,7 @@ icon: "clock"
 
 ## Description
 
-The `wait` method pauses test execution for a specified number of milliseconds before continuing. This is useful for adding delays between actions, waiting for animations to complete, or pausing for state changes to settle.
+The `wait` method stops the test for a number of milliseconds. Then it continues. Use this to add delays between actions, to wait for animations to complete, or to let state changes become stable.
 
 ## Syntax
 
@@ -38,8 +38,8 @@ await testdriver.wait();
 
 ## Best Practices
 
-- **Use for simple delays** — waiting for animations, transitions, or state changes after an action.
-- **Avoid for element waiting** — if you're waiting for a specific element to appear, use `find()` with a `timeout` option instead:
+- **Use it for simple delays**. Wait for animations, transitions, or state changes after an action.
+- **Do not use it to wait for an element**. If you wait for a specific element to show, use `find()` with a `timeout` option:
   ```javascript
   // ✅ Better for waiting for elements
   const element = await testdriver.find('success message', { timeout: 30000 });
@@ -48,5 +48,5 @@ await testdriver.wait();
   await testdriver.wait(5000);
   const element = await testdriver.find('success message');
   ```
-- Avoid excessively long timeouts to keep tests efficient.
-- Use sparingly — TestDriver's [redraw detection](/v7/performing-actions#waiting-for-dynamic-content) automatically waits for screen and network stability after each action.
+- Do not use very long timeouts. This keeps the tests efficient.
+- Use it only when necessary. The TestDriver [redraw detection](/performing-actions#waiting-for-dynamic-content) waits automatically for the screen and the network to become stable after each action.

package/docs/what-is-testdriver.mdx

@@ -0,0 +1,54 @@
+---
+title: "What is TestDriver?"
+description: "Reliably test your most difficult user flows"
+icon: "circle-info"
+---
+
+## The problem with usual test tools
+
+Usual test tools such as Playwright test one web application. They use one browser tab and they use selectors.
+
+But selectors are frequently not reliable, or they are not available. This makes tests weak and not stable:
+
+| Challenge | Problem | Examples |
+|-----------|---------|----------|
+| **Teams that move quickly** | They change the UI structure frequently. This breaks the CSS and XPath selectors. | Agile teams, startups, vibe-coders |
+| **Dynamic content** | You cannot select it with selectors. | AI chatbots, PDFs, images, videos |
+| **Software that you do not own** | It can have no correct accessibility attributes. | Other websites, extensions, third-party applications |
+| **Workflows with more than one application** | You cannot test them with web-only tools. | Desktop apps, browser extensions, IDEs |
+| **Visual states** | You cannot make a check of them with code selectors. | Charts, graphs, videos, images, spelling errors, UI layout |
+
+## The TestDriver solution
+
+TestDriver is a complete test platform. It handles these conditions. It has a Javascript SDK, hosted infrastructure, and debug tools. These tools make it easy to write, run, and keep tests for your most difficult user flows.
+
+### Javascript SDK
+
+This is an example of a TestDriver test. The test installs a production Chrome extension from the Chrome Web Store. Then it makes sure that the extension is in the extensions menu:
+
+```javascript Installing Loom from the Chrome Web Store
+import { describe, expect, it } from "vitest";
+import { TestDriver } from "testdriverai/vitest/hooks";
+
+describe("Chrome Extension Test", () => {
+  const testdriver = TestDriver(context);
+
+  // Launch Chrome with Loom loaded by its Chrome Web Store ID
+  await testdriver.provision.chromeExtension({
+    extensionId: 'liecbddmkiiihnedobmlmillhodjkdmb'
+  });
+
+  // Click on the extensions button (puzzle piece icon) in Chrome toolbar
+  const extensionsButton = await testdriver.find("The puzzle-shaped icon in the Chrome toolbar.");
+  await extensionsButton.click();
+
+  // Look for Loom in the extensions menu
+  const loomExtension = await testdriver.find("Loom extension in the extensions dropdown");
+  expect(loomExtension.found()).toBeTruthy();
+});
+```
+
+
+<Tip>[vitest](https://vitest.dev/) is the preferred test runner for TestDriver.</Tip>
+
+,

package/lib/environments.json

@@ -11,7 +11,7 @@
   },
   "canary": {
     "apiRoot": "https://api-canary.testdriver.ai",
-    "consoleUrl": "https://console-canary.testdriver.ai",
+    "consoleUrl": "https://console.testdriver.ai",
     "tdEnv": "production"
   },
   "stable": {

package/lib/github-comment.mjs

@@ -222,9 +222,8 @@ function getReplayGifUrl(replayUrl, replayId) {
   } else {
     // Map console URLs → API URLs for all environments
     // console-test.testdriver.ai → api-test.testdriver.ai
-    // console-canary.testdriver.ai → api-canary.testdriver.ai
-    // console.testdriver.ai → api.testdriver.ai
-    const consoleEnvMatch = replayUrl.match(/https:\/\/console-(test|canary)\.testdriver\.ai/);
+    // console.testdriver.ai → api.testdriver.ai (stable and canary share this console)
+    const consoleEnvMatch = replayUrl.match(/https:\/\/console-(test)\.testdriver\.ai/);
     if (consoleEnvMatch) {
       apiBaseUrl = `https://api-${consoleEnvMatch[1]}.testdriver.ai`;
     } else if (replayUrl.includes('console.testdriver.ai')) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@testdriverai/mcp",
-  "version": "7.11.136-test",
+  "version": "7.11.138-test",
   "description": "Next generation autonomous AI agent for end-to-end testing of web & desktop",
   "main": "sdk.js",
   "types": "sdk.d.ts",

package/scripts/generate-skills.js

@@ -1,7 +1,7 @@
 const fs = require("fs");
 const path = require("path");
 
-const docsDir = path.resolve(__dirname, "../docs/v7");
+const docsDir = path.resolve(__dirname, "../docs");
 const skillsDir = path.resolve(__dirname, "../ai/skills");
 
 console.log(`Generating skills from ${docsDir} to ${skillsDir}`);