testdriverai 5.5.5 → 5.5.7

package/docs/getting-started/vscode.mdx

@@ -1,89 +1,77 @@
 ---
-title: "Install the TestDriver.ai VSCode Extension"
-sidebarTitle: "VSCode Extension"
-description: "Comprehensive guide to installing and setting up TestDriver.ai for VSCode"
+title: "Install the TestDriver VS Code Extension"
+sidebarTitle: "VS Code Extension"
+description: "Comprehensive guide to installing and setting up TestDriver for VS Code"
 icon: "file-code"
 ---
 
-# Download the VSCode Extension
-
-The TestDriver.ai VSCode extension is available for download on our GitHub releases page. This extension integrates seamlessly with Visual Studio Code, allowing you to leverage the power of TestDriver.ai directly within your development environment.
-
 <Card
-  title="Download the VSCode Extension"
-  icon="download"
-  href="https://github.com/testdriverai/vscode/releases/latest/download/testdriver.vsix"
+  title="Get the VS Code Extension"
+  icon="link"
+  href="/getting-started/vscode"
 >
-  Get the latest version of the TestDriver.ai VSCode extension from our GitHub releases page. 
+  Turn your IDE into a powerful computer-use automation tool with our VS Code extension.
 </Card>
 
-# Install the extension
-
-1. Open Visual Studio Code.
-2. Go to the Extensions view by clicking on the Extensions icon in the Activity Bar on the side of the window or by pressing `Ctrl+Shift+X`.
-3. In the Extensions view, click on the three-dot menu in the top-right corner and select "Install from VSIX...".
-4. Navigate to the location where you downloaded the `testdriverai.vsix` file and select it.
-
-![](/images/content/vscode-install.png)
-
-# Try the Walkthrough
-
-The extension should launch a walkthrough. If it doesn't, you can manually start it by running the command `TestDriver: Start Setup Walkthrough` from the Command Palette (`Ctrl+Shift+P`).
-
-![](/images/content/vscode-walkthrough.png)
-
-# Overview
-
-![](/images/content/vscode-overview.png)
-
-- Test Pane
-  - Located in the **Activity Bar** (left-hand side of the editor).
-  - Clicking the **flask icon** opens the TestDriver test explorer.
-  - Lists all the available YAML-based test definitions.
-- Run all Tests
-  - This button runs all tests shown in the Test Explorer.
-  - Found near the top of the Test Explorer view.
-  - Especially useful for quickly validating a batch of test cases.
-- AI Test Creation
-  - New files created by TestDriver will automatically be focused in the editor.
-  - Defines an automated test script created by TestDriver.
-- AI Agent Test Preview
-  - Sidebar chat panel shows the TestDriver agent’s response to the prompt.
-  - Offers feedback, interpretation, or suggested actions for the test steps.
-  - Example: It identifies the context (e.g., a terminal is in focus) and suggests the correct automation action.
-  - Additional files modified by the agent are listed for context.
-- Test Output
-  - Terminal panel at the bottom of the screen.
-  - Displays live output from running the test file.
-  - Shows TestDriver version, current test script, and metadata like session ID.
-  - Helpful for debugging and understanding test execution flow.
-- Test History
-  - Shows a list of previously run test scripts.
-  - Allows developers to review or re-run older tests.
-  - Useful for regression testing or comparing AI-generated test iterations.
-
-# Troubleshooting
+<Steps>
+
+<Step title="Install TestDriver">
+Install the TestDriver CLI globally:  
+```bash
+npm install -g testdriverai@beta
+```
+</Step>
+
+<Step title="Initialize Your Project">
+Set up your project with:  
+```bash
+testdriverai init
+```  
+This creates a `.env` file and sample workflow files.
+</Step>
+
+<Step title="Run TestDriver in Interactive Mode">
+Start TestDriver in interactive mode to create and refine tests dynamically:  
+```bash
+testdriverai
+```  
+Once started, you can use commands like `/try`, `/undo`, and `/save` to interactively build and test your flows.
+</Step>
+
+<Step title="Define Your Test Steps">
+Use natural language to describe what you want to test. For example:  
+```
+> Open Google Chrome and search for "testdriverai"
+```
+TestDriver will generate steps like:  
+```yaml
+- command: focus-application
+  name: Google Chrome
+- command: hover-text
+  text: Search Google or type a URL
+  description: main search bar
+  action: click
+- command: type
+  text: testdriverai
+- command: press-keys
+  keys: [enter]
+```
+</Step>
+
+<Step title="Refine and Save Your Test">
+- Use `/undo` to remove the last step if needed.  
+- Save your test with `/save` to generate a reusable YAML file.
+</Step>
+
+<Step title="Run Saved Tests">
+Once saved, you can run your test file anytime:  
+```bash
+testdriverai run path/to/test.yml
+```
+</Step>
+
+</Steps>
 
-## I don't have GitHub Copilot Chat
-
-You can still use the extension to run and manage tests. Use the CLI for test creation instead.
-
-## The @testdriverai command doesn't show up
-
-Make sure the GitHub Copilot Chat is set to "ask."
-
-![](/images/content/vscode-ask.png)
-
-## How do I stop a running execution?
-
-Click on the "Stop" button in the bottom of agent chat.
-
-![](/images/content/vscode-stop-chat.png)
-
-Click on the "Stop" button in the top right corner of the test execution. This only shows on hover.
-
-![](/images/content/vscode-stop-test.png)
-
-A TestDriver icon will show in the tray bar. Click it, then click "quit."
+---
 
-![](/images/content/vscode-stop-quit.png)
+**Pro Tip:** Always start with interactive mode (`testdriverai`) to explore and refine your tests before saving them. It's faster and more intuitive!

package/docs/getting-started/writing.mdx

@@ -5,7 +5,7 @@ description: "Create tests with the help of TestDriver's interactive computer-us
 icon: "glasses"
 ---
 
-The TestDriver.ai interactive CLI allows you to create, refine, and execute tests dynamically using natural language commands. Here's how to get started.
+The TestDriver interactive CLI allows you to create, refine, and execute tests dynamically using natural language commands. Here's how to get started.
 
 ### Prepare Your Environment
 
@@ -21,7 +21,9 @@ When you enter commands into TestDriver, the current window will minimize and th
 
 For now, set up your environment with a browser window and your terminal side by side like so:
 
-![Terminal and Browser Side by Side](/images/content/side-by-side.webp)
+<Frame caption="Left or right, it doesn't matter!">
+<img height="200" src="/images/content/side-by-side.png" />
+</Frame>
 
 #### Application State
 
@@ -42,7 +44,7 @@ Run the following command to launch the TestDriver interactive mode:
 ```bash
 testdriverai
 ```
-You’ll see a prompt (`>`) where you can enter commands.
+You'll see a prompt (`>`) where you can enter commands.
 
 ### Write Tests Using Natural Language
 
@@ -80,7 +82,7 @@ command='hover-text' text='Sign Up' description='button in the header' action='c
 
 ### 4. Refine Your Test
 
-If something doesn’t work as intended:
+If something doesn't work as intended:
 
 - Use `/undo` to remove the last step:
   ```
@@ -91,7 +93,7 @@ Modify your prompt or add new steps to refine the test.
 
 ### 5. Save Your Test
 
-Once you’re satisfied with the test, save it to a YAML file:
+Once you're satisfied with the test, save it to a YAML file:
 
 ```
 > /save

package/docs/guide/assertions.mdx

@@ -1,13 +1,13 @@
 ---
-title: "Using Assertions in TestDriver.ai"
+title: "Using Assertions in TestDriver"
 sidebarTitle: "Assertions"
-description: "Comprehensive guide to understanding and implementing assertions in TestDriver.ai for robust test validation."
+description: "Comprehensive guide to understanding and implementing assertions in TestDriver for robust test validation."
 icon: "square-check"
 ---
 
-# Guide: Using Assertions in TestDriver.ai
+# Guide: Using Assertions in TestDriver
 
-Assertions in TestDriver.ai allow you to validate that your application behaves as expected during a test. By using the `assert` command and visual assertions, you can ensure that specific conditions are met, such as verifying the presence of text, images, or UI elements on the screen.
+Assertions in TestDriver allow you to validate that your application behaves as expected during a test. By using the `assert` command and visual assertions, you can ensure that specific conditions are met, such as verifying the presence of text, images, or UI elements on the screen.
 
 ---
 
@@ -15,7 +15,7 @@ Assertions in TestDriver.ai allow you to validate that your application behaves
 
 Assertions are checks that validate whether a specific condition is true. If the condition isn't met, the test will fail, providing feedback on what went wrong.
 
-### Types of Assertions in TestDriver.ai:
+### Types of Assertions in TestDriver:
 1. **Text Assertions**: Verify that specific text is visible on the screen.
 2. **Visual Assertions**: Validate the presence of images, icons, or UI elements.
 3. **Custom Assertions**: Use descriptive conditions to check for specific outcomes.
@@ -164,7 +164,7 @@ steps:
 ## Debugging Assertions
 
 1. **Review Error Messages**:
-   - If an assertion fails, TestDriver.ai provides detailed error messages to help identify the issue.
+   - If an assertion fails, TestDriver provides detailed error messages to help identify the issue.
 
 2. **Use Visual Feedback**:
    - Leverage screenshots and visual feedback to verify the state of the application during the assertion.

package/docs/guide/authentication.mdx

@@ -1,15 +1,19 @@
 ---
-title: "Authentication in TestDriver.ai"
+title: "Authentication in TestDriver"
 sidebarTitle: "Authentication"
-description: "Learn how to securely handle authentication workflows in TestDriver.ai using GitHub Actions."
-icon: "lock"
+description: "Learn how to securely handle authentication workflows in TestDriver using GitHub Actions."
+icon: "fingerprint"
 ---
 
-This guide explains how to handle **authentication workflows** in **TestDriver.ai** using GitHub Actions. It covers securely passing credentials (e.g., usernames and passwords) to the TestDriver.ai action and using them in both the `prerun` script and test files.
+import GitignoreWarning from '/snippets/gitignore-warning.mdx';
+
+This guide explains how to handle **authentication workflows** in **TestDriver** using GitHub Actions. It covers securely passing credentials (e.g., usernames and passwords) to the TestDriver action and using them in both the `prerun` script and test files. Save these locally in your `.env` file and use them in CI as Github secrets.
+
+<GitignoreWarning/>
 
 ---
 
-## How Authentication Works in TestDriver.ai
+## How Authentication Works in TestDriver
 
 1. **Store Credentials Securely**:
   - Use GitHub Secrets to store sensitive information like usernames, passwords, or API keys.
@@ -24,8 +28,8 @@ This guide explains how to handle **authentication workflows** in **TestDriver.a
 2. Add the following secrets:
    - **`TD_USERNAME`**: The username for login.
    - **`TD_PASSWORD`**: The password for login.
-   - **`TESTDRIVER_API_KEY`**: Your TestDriver.ai API key.
-   - **`WEBSITE_URL`**: The URL of the website to test.
+   - **`TD_API_KEY`**: Your TestDriver API key.
+   - **`TD_WEBSITE`**: The URL of the website to test.
 
 ## Step 2: Pass Credentials to the Workflow
 
@@ -36,7 +40,7 @@ Secrets are passed to the GitHub Action using the `secrets` context. They can be
 ### Example Workflow:
 
 ```yaml
-name: TestDriver.ai / Authentication
+name: TestDriver / Authentication
 
 on:
   push:
@@ -56,7 +60,7 @@ jobs:
       - name: Run Authentication Test
         uses: testdriverai/action@main
         with:
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
           prompt: |
             1. Open the login page
             2. Enter the username: ${{ secrets.TD_USERNAME }}
@@ -67,7 +71,7 @@ jobs:
             cd $env:TEMP
             npm init -y
             npm install dashcam-chrome
-            Start-Process "msedge" -ArgumentList "--start-maximized", "--load-extension=$(pwd)/node_modules/dashcam-chrome/build", "${{ secrets.WEBSITE_URL }}"
+            Start-Process "msedge" -ArgumentList "--start-maximized", "--load-extension=$(pwd)/node_modules/dashcam-chrome/build", "${{ secrets.TD_WEBSITE }}"
             exit
         env:
           TD_USERNAME: ${{ secrets.TD_USERNAME }}
@@ -110,15 +114,15 @@ steps:
 ## How It Works Together
 
 1. **Secrets in the Workflow**:
-  - Secrets like `TD_USERNAME` and `TD_PASSWORD` are passed as environment variables to the TestDriver.ai action.
+  - Secrets like `TD_USERNAME` and `TD_PASSWORD` are passed as environment variables to the TestDriver action.
 
 2. **Secrets in the `prerun` Script**:
-  - The `WEBSITE_URL` secret is used to launch the browser with the correct URL.
+  - The `TD_WEBSITE` secret is used to launch the browser with the correct URL.
 
 3. **Secrets in the Test File**:
   - The test file dynamically references the secrets to fill in login credentials during the test.
 
-## Benefits of Using Authentication in TestDriver.ai
+## Benefits of Using Authentication in TestDriver
 
 1. **Secure Handling of Credentials**:
   - Secrets are encrypted and not exposed in logs.
@@ -132,4 +136,4 @@ steps:
 
 ---
 
-By securely passing credentials and using them in the `prerun` script and test files, you can automate authentication workflows in TestDriver.ai while ensuring sensitive information remains protected.
+By securely passing credentials and using them in the `prerun` script and test files, you can automate authentication workflows in TestDriver while ensuring sensitive information remains protected.

package/docs/guide/code.mdx

@@ -1,11 +1,11 @@
 ---
-title: "Custom Code in TestDriver.ai"
+title: "Custom Code in TestDriver"
 sidebarTitle: "Custom Code"
-description: "Learn how to integrate custom Node.js scripts into your TestDriver.ai workflows for dynamic testing."
+description: "Learn how to integrate custom Node.js scripts into your TestDriver workflows for dynamic testing."
 icon: "code"
 ---
 
-TestDriver.ai allows you to execute custom **Node.js** scripts and shell scripts within your test workflows using the `exec` command. This feature, introduced in version `5.1.0`, enables you to integrate custom logic, such as generating one-time passwords (OTPs), hitting APIs, or performing other dynamic operations, directly into your tests.
+TestDriver allows you to execute custom **Node.js** scripts and shell scripts within your test workflows using the `exec` command. This feature, introduced in version `5.1.0`, enables you to integrate custom logic, such as generating one-time passwords (OTPs), hitting APIs, or performing other dynamic operations, directly into your tests.
 
 ## Key Features
 

package/docs/guide/environment-variables.mdx

@@ -0,0 +1,64 @@
+---
+title: "Environment Variables"
+sidebarTitle: "Environment Variables"
+description: "Learn how which environment variables are supported by TestDriver."
+icon: "key"
+---
+
+import GitignoreWarning from '/snippets/gitignore-warning.mdx'
+
+
+The supported environment variables in TestDriver are:
+
+| Variable | Type |         Description          |
+|:--------:|:----:|:----------------------------|
+| `TD_SPEAK` | `boolean` | Use text to speech to hear TestDriver speak as commands are run. Helpful when you don't use `TD_OVERLAY` and just plain fun. |
+| `TD_ANALYTICS` | `boolean` | Send analytics to TestDriver servers. |
+| `TD_NOTIFY` | `boolean` | Send desktop notifications when commands are run. |
+| `TD_MINIMIZE` | `boolean` | When not using VMs, minimize the terminal window / calling app when running commands. Useful if you only have one monitor, you don't want the terminal to show up. |
+| `TD_API_ROOT` | `string` | Developer only. Set API root to another URL. For on-prem. |
+| `TD_API_KEY` | `string` | Set this to spawn VMs with TestDriver Pro. |
+| `TD_OVERLAY` | `boolean` | Spawn overlay window that shows both the TestDriver console output, and draws the cursor and squares on the screen as TestDriver thinks. Defaults to true if not provided.|
+| `TD_VM` | `boolean` | Run commands in a Linux VM instead of on own desktop. Requires API key. |
+| `TD_VM_RESOLUTION` | `number[]` | Change resolution when TD_VM is true. |
+| `TD_TYPE` | `string` | Set the type of test to run. Can be `website`, `desktop`, or `mobile`. Not required. |
+
+<GitignoreWarning />
+
+---
+## Example
+```
+TD_VM=true
+TD_API_KEY=your_api_key
+TD_VM_RESOLUTION=[1024,768]
+TD_MINIMIZE=true
+TD_TYPE=website
+TD_WEBSITE=www.jeep.com
+TD_ANALYTICS=true
+TD_OVERLAY=false
+
+```
+In this example `.env` file, we are running a website test in a local Linux VM with a resolution of 1024x768. The terminal will be minimized, and the overlay will not be shown. Analytics will be sent to TestDriver servers.
+
+---
+## Using Environment Variables in Deployed tests
+When running tests in a deployed environment, you can set environment variables in the `env` section of your GitHub Actions workflow file. This allows you to customize the behavior of TestDriver based on the environment in which it's running. Setup any environment variables you plan to use in the deployed test in your `.env` file and add them  as Github secrets. 
+
+<Tip>For more info on how to set up environment variables with Github Actions, see [Managing Secrets in GitHub Actions](/actions/secrets)</Tip>
+
+In this example, there is both a `TD_TEST_USERNAME` and `TD_TEST_PASSWORD` variables in the local `.env` file. This file is used to run tests locally and mask credentials used to log in to a website. When deployed, these variables are stored as secrets in GitHub and are passed to the TestDriver action when it runs.
+
+---
+## Example 2 
+
+```
+TD_VM=false
+TD_MINIMIZE=true
+TD_WEBSITE=www.rollsroyce.com
+TD_ANALYTICS=false
+TD_OVERLAY=true
+TD_TEST_USERNAME=me@mysite.com
+TD_TEST_PASSWORD=wokeupinanewbugatti
+```
+
+In this example `.env` file, we are running a website test with our desktop using the local agent. The terminal will be minimized, and the overlay will be shown. Analytics will not be sent to TestDriver servers. The `TD_TEST_USERNAME` and `TD_TEST_PASSWORD` variables are used to log in to the website. Be sure to expand these in your test with `${TD_TEST_USERNAME}` and `${TD_TEST_PASSWORD}` notation!

package/docs/guide/lifecycle.mdx

@@ -36,6 +36,160 @@ steps:
         timeout: 30000
 ```
 
+
 ### Notes
 
 - Currently, there is no teardown task implemented. However, when running on GitHub Actions, the virtual machine (VM) is ephemeral, meaning everything is destroyed after the test run.
+
+
+## Advanced Configuration
+If you need to perform more complex setup or teardown tasks, you can use the `lifecycle` folder in your repository. This folder can contain multiple files, each with a specific purpose.
+
+## Workflow Overview
+
+1. **Setup Tasks**:
+   - Use a dedicated action **before** the TestDriver action to prepare the environment (e.g., create a test user via an API).
+   - Pass the created user credentials to the TestDriver action using environment variables.
+
+2. **Run Tests**:
+   - Execute the tests using TestDriver, leveraging the setup data (e.g., the test user).
+
+3. **Teardown Tasks**:
+   - Use a dedicated action **after** the TestDriver action to clean up (e.g., delete the test user).
+   - Ensure the teardown step runs **no matter the result** of the TestDriver action.
+
+---
+
+## Example Workflow with Advanced Setup and Teardown
+
+### Workflow File: `.github/workflows/testdriver-setup-teardown.yml`
+
+```yaml
+name: TestDriver with Setup and Teardown
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  test:
+    name: "TestDriver with Setup and Teardown"
+    runs-on: ubuntu-latest
+    steps:
+      # Step 1: Check out the repository
+      - name: Check out repository
+        uses: actions/checkout@v2
+
+      # Step 2: Setup - Create a test user via API
+      - name: Setup Test User
+        id: setup-user
+        run: |
+          echo "Creating test user via API..."
+          RESPONSE=$(curl -X POST -H "Content-Type: application/json" -d '{"name": "Test User", "email": "test@example.com", "password": "password123"}' https://api.example.com/users)
+          echo "USER_ID=$(echo $RESPONSE | jq -r '.id')" >> $GITHUB_ENV
+          echo "USER_EMAIL=$(echo $RESPONSE | jq -r '.email')" >> $GITHUB_ENV
+          echo "USER_PASSWORD=password123" >> $GITHUB_ENV
+        env:
+          API_KEY: ${{ secrets.API_KEY }}
+
+      # Step 3: Run Tests with TestDriver
+      - name: Run Tests with TestDriver
+        uses: testdriverai/action@main
+        with:
+          key: ${{ secrets.TD_API_KEY }}
+          prompt: |
+            1. Log in with the test user
+            2. Perform actions on the dashboard
+          prerun: |
+            echo "Launching browser with test user credentials..."
+            echo "Email: $USER_EMAIL"
+            echo "Password: $USER_PASSWORD"
+        env:
+          USER_EMAIL: ${{ env.USER_EMAIL }}
+          USER_PASSWORD: ${{ env.USER_PASSWORD }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          FORCE_COLOR: "3"
+
+      # Step 4: Teardown - Delete the test user
+      - name: Teardown Test User
+        if: always()
+        run: |
+          echo "Deleting test user via API..."
+          curl -X DELETE -H "Authorization: Bearer ${{ secrets.API_KEY }}" https://api.example.com/users/$USER_ID
+          echo "Test user deleted."
+        env:
+          USER_ID: ${{ env.USER_ID }}
+          API_KEY: ${{ secrets.API_KEY }}
+```
+
+---
+
+## Workflow Steps Explained
+
+### 1. **Setup Test User**
+- **Purpose**: Create a test user via an API before running the tests.
+- **How It Works**:
+  - The `Setup Test User` step sends a `POST` request to the API to create a new user.
+  - The user ID, email, and password are extracted from the API response and stored as environment variables (`USER_ID`, `USER_EMAIL`, `USER_PASSWORD`).
+- **Example Output**:
+  - `USER_ID`: `12345`
+  - `USER_EMAIL`: `test@example.com`
+  - `USER_PASSWORD`: `password123`
+
+---
+
+### 2. **Run Tests with TestDriver**
+- **Purpose**: Execute tests using the TestDriver action.
+- **How It Works**:
+  - The `USER_EMAIL` and `USER_PASSWORD` environment variables are passed to the `prerun` script.
+  - The test prompts use these credentials to log in and perform actions.
+
+---
+
+### 3. **Teardown Test User**
+- **Purpose**: Delete the test user via an API after the tests are complete.
+- **How It Works**:
+  - The `Teardown Test User` step sends a `DELETE` request to the API to remove the test user.
+  - The `if: always()` condition ensures this step runs even if the TestDriver action fails.
+
+---
+
+## Best Practices for Setup and Teardown
+
+1. **Use APIs for Setup and Teardown**:
+   - Use APIs to create and delete test data dynamically, ensuring a clean environment for each test run.
+
+2. **Pass Data via Environment Variables**:
+   - Store setup data (e.g., user credentials) in environment variables and pass them to the TestDriver action.
+
+3. **Ensure Teardown Always Runs**:
+   - Use `if: always()` to ensure teardown tasks are executed regardless of the test results.
+
+4. **Log Setup and Teardown Steps**:
+   - Add `echo` statements to log the progress of setup and teardown tasks for easier debugging.
+
+5. **Test Locally**:
+   - Verify setup and teardown scripts locally before integrating them into the workflow.
+
+---
+
+## Example Use Cases
+
+### 1. **User Management**
+- Create a test user during setup.
+- Delete the test user during teardown.
+
+### 2. **Database Operations**
+- Insert test data into a database during setup.
+- Remove the test data during teardown.
+
+### 3. **Mock Services**
+- Start a mock API server during setup.
+- Stop the mock server during teardown.
+
+---
+
+By structuring your workflow to handle **setup** before the TestDriver action and **teardown** after it, you can ensure a clean and reliable test environment for every run. This approach also ensures that teardown tasks are executed regardless of the test results, maintaining a consistent state for subsequent runs.

package/docs/guide/locating.mdx

@@ -1,11 +1,11 @@
 ---
-title: "Locating Elements in TestDriver.ai"
+title: "Locating Elements in TestDriver"
 sidebarTitle: "Locating Elements"
-description: "Learn how to effectively describe and locate elements using TestDriver.ai's visual understanding capabilities."
+description: "Learn how to effectively describe and locate elements using TestDriver's visual understanding capabilities."
 icon: "magnifying-glass"
 ---
 
-TestDriver.ai uses **visual understanding** to locate elements on the screen. Unlike traditional testing frameworks that rely on selectors or element IDs, TestDriver.ai identifies elements based on their **visual appearance**. This guide explains how to describe elements effectively to ensure TestDriver.ai can locate them accurately.
+TestDriver uses **visual understanding** to locate elements on the screen. Unlike traditional testing frameworks that rely on selectors or element IDs, TestDriver identifies elements based on their **visual appearance**. This guide explains how to describe elements effectively to ensure TestDriver can locate them accurately.
 
 ---
 
@@ -24,7 +24,7 @@ TestDriver.ai uses **visual understanding** to locate elements on the screen. Un
    - For icons or images, describe their shape, color, or associated label.
 
 4. **Leverage Visual Feedback**:
-   - TestDriver.ai will draw **yellow boxes** around detected elements during test execution.
+   - TestDriver will draw **yellow boxes** around detected elements during test execution.
    - Use this feedback to verify that the correct element is being targeted.
 
 ---
@@ -53,7 +53,7 @@ TestDriver.ai uses **visual understanding** to locate elements on the screen. Un
 
 ---
 
-## How to Write TestDriver.ai Commands
+## How to Write TestDriver Commands
 
 ### Example: Locating a Button
 
@@ -105,8 +105,8 @@ TestDriver.ai uses **visual understanding** to locate elements on the screen. Un
 ## Debugging Element Detection
 
 1. **Run the Test**:
-   - Execute the test using TestDriver.ai.
-   - TestDriver.ai will draw **yellow boxes** around detected elements.
+   - Execute the test using TestDriver.
+   - TestDriver will draw **yellow boxes** around detected elements.
 
 2. **Verify the Correct Element**:
    - Ensure the yellow box highlights the intended element.
@@ -127,11 +127,11 @@ TestDriver.ai uses **visual understanding** to locate elements on the screen. Un
    - Run tests after adding or modifying commands to verify element detection.
 
 3. **Use Visual Feedback**:
-   - Leverage the yellow boxes drawn by TestDriver.ai to confirm the correct element is being targeted.
+   - Leverage the yellow boxes drawn by TestDriver to confirm the correct element is being targeted.
 
 4. **Avoid Overloading Descriptions**:
    - Keep descriptions concise but detailed enough to uniquely identify the element.
 
 ---
 
-By focusing on **visual descriptions** and leveraging TestDriver.ai's feedback, you can accurately locate elements and create robust, reliable tests.
+By focusing on **visual descriptions** and leveraging TestDriver's feedback, you can accurately locate elements and create robust, reliable tests.