@testdriverai/mcp 7.11.136-test → 7.11.138-test

package/docs/{v7/generating-tests.mdx → generating-tests.mdx}

@@ -1,21 +1,21 @@
 ---
 title: "Explore"
-sidebarTitle: "Explore"
+sidebarTitle: "Generating tests"
 description: "Generate tests by exploring your app with the AI vision agent"
 icon: "compass"
 ---
 
-Start by exploring your app. This is where tests begin: you describe a flow in plain English, and the TestDriver vision agent clicks, types, and reads the screen to figure it out — then writes the test for you. No selectors, no DOM, no brittle locators. Just describe what you want to test and let the agent discover the rest.
+Start with an exploration of your app. Tests begin here: you describe a flow in plain English. Then the TestDriver vision agent clicks, types, and reads the screen to understand it. Then it writes the test for you. There are no selectors, no DOM, and no weak locators. Only describe what you want to test. Let the agent find the other parts.
 
-There are two ways to explore: chatting interactively with your AI assistant through the TestDriver MCP server, or handing a coding agent our instructions file and prompting it to generate a test.
+There are two methods for an exploration. You can chat with your AI assistant through the TestDriver MCP server. Or you can give a coding agent our instructions file and tell it to generate a test.
 
 <Info>
-  Both paths need an MCP-capable AI coding assistant. If you don't have one yet, start with **GitHub Copilot** — there's a [free tier](https://github.com/features/copilot/plans), no credit card required. See [Run → Setup](/v7/copilot/running-tests#setup) for the full install and sign-in walkthrough.
+  Both paths need an MCP-capable AI coding assistant. If you don't have one yet, start with **GitHub Copilot** — there's a [free tier](https://github.com/features/copilot/plans), no credit card required. See [Run → Setup](/copilot/running-tests#setup) for the full install and sign-in walkthrough.
 </Info>
 
 ## Instructions for Coding Agents
 
-We recommend starting with [our quickstart](./quickstart), then supplying your coding agent with our agent instructions file.
+Start with [our quickstart](./quickstart). Then give your coding agent our agent instructions file.
 
 <Card title="TestDriver Agent Instructions" icon="link" arrow="true" horizontal href="https://github.com/testdriverai/testdriverai/blob/main/ai/agents/testdriver.md?plain=1">
   Copy the current version of our agent instructions to provide your coding agent with up-to-date instructions on how to generate TestDriver tests.
@@ -33,13 +33,13 @@ Push Submit button
 Verify new page contains expected text 'logged in'
 ```
 
-<Info>Explicit commands are preferred for production tests, as they are cheaper, faster, and more reliable.</Info>
+<Info>Use explicit commands for production tests. They are at a lower cost, faster, and more reliable.</Info>
 
 ## Start a Conversation
 
-With TestDriver's MCP server and your AI assistant (GitHub Copilot, Cursor, or Claude Desktop), you can create tests by chatting with an AI agent. The agent spawns a virtual machine, executes actions, and writes test code for you.
+Use the TestDriver MCP server and your AI assistant (GitHub Copilot, Cursor, or Claude Desktop) to make tests. You chat with an AI agent. The agent starts a virtual machine, does actions, and writes the test code for you.
 
-Open your AI assistant's chat. If your project has no other agents configured, the TestDriver agent is used by default. Otherwise, select **testdriver** from the agent dropdown in the chat panel.
+Open the chat of your AI assistant. If your project has no other agents, TestDriver uses the TestDriver agent by default. If not, select **testdriver** from the agent dropdown in the chat panel.
 
 Describe what you want to test:
 
@@ -66,7 +66,7 @@ When the agent starts a session, a **live preview panel** opens in your editor.
 - **Debug issues** — see exactly what the AI sees
 
 <Note>
-  The live preview panel requires the TestDriver VS Code extension. Set `TD_PREVIEW=ide` in your MCP configuration to enable it. See the [Run page](/v7/copilot/running-tests) for all device and preview options.
+  The live preview panel requires the TestDriver VS Code extension. Set `TD_PREVIEW=ide` in your MCP configuration to enable it. See the [Run page](/copilot/running-tests) for all device and preview options.
 </Note>
 
 ## Interactive Workflow
@@ -187,6 +187,6 @@ describe("Login Flow", () => {
 
 ## Next
 
-<Card title="Learn" icon="brain" arrow="true" horizontal href="/v7/caching">
+<Card title="Learn" icon="brain" arrow="true" horizontal href="/caching">
   Once the agent has explored your app, TestDriver caches what it discovers so your tests replay instantly without re-reasoning over the screen every time.
 </Card>

package/docs/guide/best-practices-polling.mdx

@@ -1,4 +1,9 @@
-# Best Practices: Element Polling
+---
+title: "Waiting for Elements"
+sidebarTitle: "Waiting for Elements"
+description: "Prefer find() with a timeout over fixed wait() delays when waiting for elements to appear."
+icon: "hourglass-half"
+---
 
 **When waiting for elements to appear, prefer `find()` with a `timeout` option over `wait()`.**
 

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

@@ -6,11 +6,11 @@ icon: "cloud"
 mode: "wide"
 ---
 
-Hosted pricing is based on **device-seconds**: the amount of time your tests run on **our infrastructure**.
+The hosted price uses **device-seconds**: the time that your tests run on **our infrastructure**.
 
-- **Zero Setup** — Start testing immediately. No DevOps required.
-- **Free Tier** — Get started with a limited preview at no cost.
-- **Pay As You Go** — Only pay for the device-seconds you use.
+- **Zero Setup**. Start tests immediately. You do not need DevOps.
+- **Free Tier** — Start with a limited preview at no cost.
+- **Pay As You Go** — Pay only for the device-seconds that you use.
 
 ## Hosted Plans
 
@@ -53,7 +53,7 @@ Hosted is the default when you follow the Quickstart guide.
 <Card
   title="Try the Quickstart"  
   icon="play"
-  href="/v7/quickstart"
+  href="/quickstart"
 >
   Set your API key and start testing in minutes.
 </Card>
@@ -139,7 +139,7 @@ To prevent tests from failing due to exceeding your license slot limit, we recom
 
 ## When to Consider Self-Hosted
 
-Hosted is perfect for getting started and for teams that want zero infrastructure management. However, you might consider [Self-Hosted](/v7/self-hosted) if you:
+Hosted is perfect for getting started and for teams that want zero infrastructure management. However, you might consider [Self-Hosted](/self-hosted) if you:
 
 - Want to escape per-second billing with a flat license fee
 - Require greater concurrency than offered in Cloud plans
@@ -151,7 +151,7 @@ Hosted is perfect for getting started and for teams that want zero infrastructur
 <Card
   title="Explore Self-Hosted"
   icon="server"
-  href="/v7/self-hosted"
+  href="/self-hosted"
 >
   Learn about self-hosting for unlimited test execution at a flat rate.
 </Card>

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

@@ -7,11 +7,11 @@ icon: "hand-pointer"
 
 ## Overview
 
-Move the mouse cursor over elements or specific coordinates without clicking, useful for revealing tooltips, dropdowns, and hover effects.
+Move the mouse cursor onto elements or coordinates without a click. Use this to show tooltips, dropdowns, and hover effects.
 
 ## Element Hover
 
-Hover over a located element.
+Put the cursor on a found element.
 
 ### Syntax
 
@@ -43,7 +43,7 @@ await submenu.click();
 
 ## Coordinate Hover
 
-Hover at specific screen coordinates.
+Put the cursor at screen coordinates.
 
 ### Syntax
 
@@ -274,6 +274,6 @@ describe('Hover Interactions', () => {
 
 ## Related Methods
 
-- [`find()`](/v7/find) - Locate elements to hover
-- [`click()`](/v7/click) - Click after hovering
-- [`mouseDown()`](/v7/click) - Start drag operations
+- [`find()`](/find) - Locate elements to hover
+- [`click()`](/click) - Click after hovering
+- [`mouseDown()`](/click) - Start drag operations

package/docs/interacting-with-your-app.mdx

@@ -0,0 +1,198 @@
+---
+title: "Interacting With Your App"
+sidebarTitle: "Interacting With Your App"
+description: "Click, hover, drag, and interact with located UI elements"
+icon: "hand-pointer"
+---
+
+## Overview
+
+Once you've [located an element](/locating-elements), the `Element` object exposes methods to interact with it. Use these to click, hover, and perform mouse operations that drive your app.
+
+## Interaction Methods
+
+#### click()
+
+Click on the element.
+
+```javascript
+await element.click(action)
+```
+
+**Parameters:**
+- `action` (string, optional) - Type of click: `'click'` (default), `'double-click'`, `'right-click'`, `'hover'`, `'mouseDown'`, `'mouseUp'`
+
+**Returns:** `Promise<void>`
+
+**Example:**
+```javascript
+const button = await testdriver.find('submit button');
+await button.click(); // Regular click
+
+const file = await testdriver.find('document.txt');
+await file.click('double-click'); // Double-click
+
+const menu = await testdriver.find('settings icon');
+await menu.click('right-click'); // Right-click
+```
+
+<Note>
+  The element must be found before clicking. The `find()` method automatically locates the element.
+</Note>
+
+#### hover()
+
+Hover over the element without clicking.
+
+```javascript
+await element.hover()
+```
+
+**Returns:** `Promise<void>`
+
+**Example:**
+```javascript
+const tooltip = await testdriver.find('info icon');
+await tooltip.hover();
+// Wait to see tooltip
+await new Promise(resolve => setTimeout(resolve, 1000));
+```
+
+#### doubleClick()
+
+Double-click on the element.
+
+```javascript
+await element.doubleClick()
+```
+
+**Returns:** `Promise<void>`
+
+**Example:**
+```javascript
+const file = await testdriver.find('README.txt file icon');
+await file.doubleClick();
+```
+
+#### rightClick()
+
+Right-click on the element to open context menu.
+
+```javascript
+await element.rightClick()
+```
+
+**Returns:** `Promise<void>`
+
+**Example:**
+```javascript
+const folder = await testdriver.find('Documents folder');
+await folder.rightClick();
+```
+
+#### mouseDown() / mouseUp()
+
+Press or release mouse button on the element (for drag operations).
+
+```javascript
+await element.mouseDown()
+await element.mouseUp()
+```
+
+**Returns:** `Promise<void>`
+
+**Example:**
+```javascript
+// Drag and drop
+const item = await testdriver.find('draggable item');
+await item.mouseDown();
+
+// Move to drop target (using coordinates or another element)
+const target = await testdriver.find('drop zone');
+await target.hover();
+await target.mouseUp();
+```
+
+## Examples
+
+### Basic Element Interaction
+
+```javascript
+// Find and click
+const submitButton = await testdriver.find('submit button');
+await submitButton.click();
+
+// Find, verify, then interact
+const emailInput = await testdriver.find('email input field');
+if (emailInput.found()) {
+  await emailInput.click();
+  await testdriver.type('user@example.com');
+}
+```
+
+### Working with Forms
+
+```javascript
+// Fill out a multi-field form
+const nameField = await testdriver.find('name input field');
+await nameField.click();
+await testdriver.type('John Doe');
+
+const emailField = await testdriver.find('email input field');
+await emailField.click();
+await testdriver.type('john@example.com');
+
+const submitButton = await testdriver.find('submit button');
+await submitButton.click();
+```
+
+### Conditional Interactions
+
+```javascript
+// Check if element exists before interacting
+const closeButton = await testdriver.find('close popup button');
+
+if (closeButton.found()) {
+  await closeButton.click();
+  console.log('Popup closed');
+} else {
+  console.log('No popup to close');
+}
+```
+
+### Re-locating Dynamic Elements
+
+```javascript
+// Element that moves or changes
+const notification = await testdriver.find('success notification');
+
+// Do something that might cause it to move
+await testdriver.scroll('down', 300);
+
+// Re-locate the element
+await notification.find();
+
+if (notification.found()) {
+  await notification.click();
+}
+```
+
+## Best Practices
+
+<AccordionGroup>
+  <Accordion title="Reuse element references when possible">
+    If you need to interact with the same element multiple times, reuse the reference:
+    
+    ```javascript
+    const input = await testdriver.find('search input');
+    await input.click();
+    await testdriver.type('first search');
+    await testdriver.pressKeys(['enter']);
+    
+    // Re-use the same element reference
+    await input.click();
+    await testdriver.pressKeys(['ctrl', 'a']); // Select all
+    await testdriver.type('second search');
+    ```
+  </Accordion>
+</AccordionGroup>