testdriverai 6.1.7 → 6.1.8-canary.68bcfa2.0

package/.github/workflows/acceptance-tests.yml

@@ -7,6 +7,8 @@ on:
   # So that we don't do expensive tests until approved
   push:
     branches: [main]
+    paths-ignore:
+      - "docs/**"
   # So that we can manually trigger tests when there's flake
   workflow_dispatch:
 

package/.github/workflows/acceptance-v6.yml

@@ -5,6 +5,8 @@ on:
   push:
     branches:
       - main
+    paths-ignore:
+      - "docs/**"
   pull_request:
     branches:
       - main

package/.github/workflows/lint.yml

@@ -1,7 +1,10 @@
 # Ensure affected code follows standards and is formatted correctly. Otherwise, automatic formatting in future changes will cause larger diffs.
 name: Lint + Prettier
 
-on: push
+on:
+  push:
+    paths-ignore:
+      - "docs/**"
 
 jobs:
   lint:

package/.github/workflows/publish-canary.yml

@@ -10,6 +10,8 @@ on:
   # So that we publish for every push to `main`, despite tests
   push:
     branches: [main]
+    paths-ignore:
+      - "docs/**"
   workflow_dispatch:
 
 jobs:

package/.github/workflows/self-hosted.yml

@@ -3,6 +3,8 @@ name: AWS
 on:
   workflow_dispatch:
   push:
+    paths-ignore:
+      - "docs/**"
 
 jobs:
   gather:

package/docs/account/enterprise.mdx

@@ -24,15 +24,15 @@ We specialize in testing scenarios that other tools can't handle - desktop appli
 
 ## Enterprise Plans
 
-TestDriver Enterprise plans start at **$995/month** and include:
+TestDriver Enterprise plans start at **$2,000/month** and include:
 
+- A pilot program with our expert team to create 4 custom tests within your first 4 weeks (4x4 Guarantee).
+- 4 parallel tests
 - **12,500 runner minutes per month**: Sufficient capacity for continuous testing of your custom test suite.
-- Enterprise-grade test dashboards with advanced analytics.
 - Full CI/CD pipeline integration with custom configurations.
 - Dedicated infrastructure and ongoing support for complex testing scenarios.
-- Expert test creation and maintenance services.
 
-For detailed pricing and contract information, see [Contract Details](#contract-details). For other plans, visit our [Pricing](/account/pricing) page.
+For detailed pricing and contract information our [Pricing](/account/pricing) page. Want unlimited minutes or enhanced security? We also support self-hosted options with 16 parallel tests starting at $2,000/month. See our [Self Hosting](/getting-started/self-hosting) docs for more info.
 
 <CardGroup cols={3}>
   <Card title="Custom Desktop & Extension Testing">
@@ -66,17 +66,14 @@ TestDriver Enterprise provides comprehensive support for fast-moving teams with
 
 Testing complex applications requires more than standard automation tools. Desktop applications, browser extensions, and multi-platform workflows demand specialized infrastructure, custom integrations, and deep technical expertise. TestDriver Enterprise provides the complete solution - from initial setup through ongoing maintenance and support.
 
-For more details, see [Contract Details](#contract-details).
-
 ---
 
 ## Implementation Process
 
 1. **Initial Consultation**: Discuss your specific testing challenges, application architecture, and infrastructure requirements.
-2. **Custom Infrastructure Design**: Configure specialized testing environments tailored to your technology stack and workflow requirements.
-3. **Expert Test Development**: Our team develops 4 custom tests designed specifically for your application's critical user flows and business logic.
-4. **Integration & Deployment**: Implement tests within your CI/CD pipeline with custom monitoring and reporting configurations.
-5. **Team Training & Ongoing Support**: Comprehensive training for your team plus ongoing technical support and consultation.
+2. **Expert Test Development**: Our team develops 4 custom tests designed specifically for your application's critical user flows and business logic.
+3. **Integration & Deployment**: Implement tests within your CI/CD pipeline with custom monitoring and reporting configurations.
+4. **Team Training & Ongoing Support**: Comprehensive training for your team plus ongoing technical support and consultation.
 
 Complex applications - particularly desktop software, browser extensions, and multi-platform workflows - present unique testing challenges that require specialized infrastructure and deep technical expertise. TestDriver Enterprise addresses these challenges with custom solutions designed specifically for your application and development process.
 
@@ -86,7 +83,6 @@ Complex applications - particularly desktop software, browser extensions, and mu
 
 | Service                           | Timeline      | Description                                                                                      |
 | --------------------------------- | ------------- | ------------------------------------------------------------------------------------------------ |
-| **Infrastructure Design**         | First 7 Days  | Analysis and configuration of specialized testing environments for your application stack.       |
 | **Requirements Analysis**         | First 7 Days  | Comprehensive review of testing requirements and technical specifications.                       |
 | **Custom Test Development**       | First 4 Weeks | Expert creation of 4 fully customized tests (4x4 Guarantee) tailored to your critical workflows. |
 | **Training & Knowledge Transfer** | First 30 Days | Technical training for your team and establishment of ongoing support processes.                 |
@@ -103,7 +99,7 @@ Complex applications - particularly desktop software, browser extensions, and mu
 - **Service Level**: Dedicated support team and technical consultation included.
 - **Usage Tracking**: Monthly runner minute allocation with standard overage rates.
 - **Custom Infrastructure**: Specialized testing environments included for complex applications.
-- **Enterprise Options**: On-premises and BYOC (Bring Your Own Cloud) configurations available.
+- **Enterprise Options**: [Self hosting](/getting-started/self-hosting) configurations available.
 
 ---
 

package/docs/account/pricing.mdx

@@ -19,12 +19,12 @@ TestDriver offers a range of pricing plans to suit different needs, from individ
   </Card>
   <Card title="Enterprise" icon="shield">
     Need advanced features? Contact us for tailored solutions. Starting at
-    $995/month.
+    $2,000/month.
   </Card>
 </CardGroup>
 
 <Tip>
-  Every plan starts with $100 in TestDriver credits to get you off the starting
+  Every plan comes with access to the Playwright SDK to get you off the starting
   line!
 </Tip>
 

package/docs/account/projects.mdx

@@ -23,6 +23,11 @@ From the Project view, you can see all the replays (Dashes) stored for that proj
 
 When you create a new Project, you can also enable the <Icon icon="jira" /> Jira integration to create issues automatically each time a replay (Dash) is created.
 
+<Info>
+  The project ID can be used in conjunction with your `lifecycle/postrun.yaml`
+  script to automatically assign a replay to a project. For more info see the
+  (Dashcam section)[/guide/dashcam].
+</Info>
 <Frame caption="Click a Project to view its replays">
   <img src="/images/content/account/newprojectsettings.png" />
 </Frame>

package/docs/apps/tauri-apps.mdx

@@ -14,10 +14,7 @@ icon: "https://tauri.app/favicon.svg"
 
 In this guide, we'll leverage [Playwright](https://playwright.dev/) and the [TestDriver Playwright SDK](/getting-started/playwright) to convert the [Tauri Quick Start](https://tauri.app/start/create-project/) to TestDriver's selectorless, Vision AI.
 
-<Info>
-  View Source:
-  https://github.com/testdriverai/demo-tauri-app
-</Info>
+<Info>View Source: https://github.com/testdriverai/demo-tauri-app</Info>
 
 ### Requirements
 
@@ -30,7 +27,7 @@ To start testing your Tauri app with TestDriver, you need the following:
         You will need a [Free TestDriver Account](https://app.testdriver.ai/team) to get an API key.
 
         <Card title="Sign Up for TestDriver" icon="user-plus" horizontal href="https://app.testdriver.ai/team">
-          
+
         </Card>
       </Step>
       <Step title="Set up your environment">
@@ -54,6 +51,7 @@ To start testing your Tauri app with TestDriver, you need the following:
         </Tabs>
       </Step>
     </Steps>
+
   </Accordion>
   <Accordion title="Create a Tauri project">
     <Note>
@@ -98,6 +96,7 @@ To start testing your Tauri app with TestDriver, you need the following:
     ✔ Install Playwright browsers (can be done manually via 'npx playwright install')? (Y/n)
     > Y
     ```
+
   </Accordion>
   <Accordion title="Install the TestDriver Playwright SDK">
     `@testdriver.ai/playwright` is an AI-powered extension of `@playwright/test`.
@@ -119,6 +118,7 @@ To start testing your Tauri app with TestDriver, you need the following:
         ```
       </Tab>
     </Tabs>
+
   </Accordion>
 </AccordionGroup>
 
@@ -146,6 +146,7 @@ First, we need to modify the default Playwright configuration and our Tauri proj
       },
     });
     ```
+
   </Step>
   <Step title="Mock Tauri APIs">
     Since we're testing the Tauri frontend, we need to [mock IPC Requests](https://tauri.app/develop/tests/mocking/)
@@ -167,6 +168,7 @@ First, we need to modify the default Playwright configuration and our Tauri proj
     ```
 
     We only need to do this once, as we'll be accessing `window.mockIPC` in our tests.
+
   </Step>
   <Step title="Create a new test file">
     Create a new file (e.g. `tests/testdriver.spec.ts`) with:
@@ -174,15 +176,16 @@ First, we need to modify the default Playwright configuration and our Tauri proj
     ```typescript tests/testdriver.spec.ts
     import type { mockIPC } from "@tauri-apps/api/mocks";
     import { expect, test } from "@playwright/test";
-    
+
     test.beforeEach(async ({ page }) => {
       await page.goto("http://localhost:1420");
     });
-    
+
     test("should have title", async ({ page }) => {
       await expect(page).toHaveTitle("Tauri + React + TypeScript");
     });
     ```
+
   </Step>
   <Step title="Run Playwright in UI Mode">
     Now we're ready to run Playwright and start working on our tests:
@@ -211,6 +214,7 @@ First, we need to modify the default Playwright configuration and our Tauri proj
     <Tip>
       Click the <Icon icon="eye" /> button to automatically re-run tests on save.
     </Tip>
+
   </Step>
 </Steps>
 
@@ -300,6 +304,7 @@ With TestDriver, we can skip the test implementation **entirely** and let AI per
       });
     });
     ```
+
   </Step>
   <Step title="Add an Agentic Test">
     Next, wrap a _prompt_ in `test.agent` to perform the test:
@@ -313,6 +318,7 @@ With TestDriver, we can skip the test implementation **entirely** and let AI per
       `);
     });
     ```
+
   </Step>
 </Steps>
 
@@ -327,27 +333,13 @@ We can use TestDriver and natural language to test our Tauri desktop app:
 <Steps>
   <Step title="Run the Desktop App">
     <Tabs>
-      <Tab title="npm">
-        ```bash
-        npm run tauri dev
-        ```
-      </Tab>
-      <Tab title="yarn">
-        ```bash
-        yarn tauri dev
-        ```
-      </Tab>
-      <Tab title="pnpm">
-        ```bash
-        pnpm tauri dev
-        ```
-      </Tab>
+      <Tab title="npm">```bash npm run tauri dev ```</Tab>
+      <Tab title="yarn">```bash yarn tauri dev ```</Tab>
+      <Tab title="pnpm">```bash pnpm tauri dev ```</Tab>
     </Tabs>
   </Step>
   <Step title="Continued Reading">
-    <Note>
-      See [Desktop Apps](/apps/desktop-apps) for more information.
-    </Note>
+    <Note>See [Desktop Apps](/apps/desktop-apps) for more information.</Note>
   </Step>
 </Steps>
 
@@ -358,26 +350,12 @@ We can use TestDriver and natural language to test our Tauri iOS app:
 <Steps>
   <Step title="Run the Mobile App">
     <Tabs>
-      <Tab title="npm">
-        ```bash
-        npm run tauri ios dev
-        ```
-      </Tab>
-      <Tab title="yarn">
-        ```bash
-        yarn tauri ios dev
-        ```
-      </Tab>
-      <Tab title="pnpm">
-        ```bash
-        pnpm tauri ios dev
-        ```
-      </Tab>
+      <Tab title="npm">```bash npm run tauri ios dev ```</Tab>
+      <Tab title="yarn">```bash yarn tauri ios dev ```</Tab>
+      <Tab title="pnpm">```bash pnpm tauri ios dev ```</Tab>
     </Tabs>
   </Step>
   <Step title="Continued Reading">
-    <Note>
-      See [Mobile Apps](/apps/mobile-apps) for more information.
-    </Note>
+    <Note>See [Mobile Apps](/apps/mobile-apps) for more information.</Note>
   </Step>
-</Steps>
+</Steps>

package/docs/cli/overview.mdx

@@ -15,11 +15,11 @@ npx testdriverai@latest <command> [options]
 
 ## Available commands
 
-|        Command         | Description                                                  |
-| :--------------------: | :----------------------------------------------------------- |
-| [`run`](/commands/run) | Executes a TestDriver test.                                  |
-| [`edit`](/commands/edit)         | Launch interactive mode.                                     |
-| [`help`](/commands/help)         | Displays help information for the CLI or a specific command. |
+|         Command          | Description                                                  |
+| :----------------------: | :----------------------------------------------------------- |
+|  [`run`](/commands/run)  | Executes a TestDriver test.                                  |
+| [`edit`](/commands/edit) | Launch interactive mode.                                     |
+| [`help`](/commands/help) | Displays help information for the CLI or a specific command. |
 
 ## Available Flags
 
@@ -27,10 +27,9 @@ npx testdriverai@latest <command> [options]
 | :------------------ | :----------------------------------------------------------------------------------------- |
 | `--heal`            | Launch exploratory mode and attemp to recover if an error or failing state is encountered. |
 | `--write`           | Ovewrite test file with new commands resulting from agentic testing                        |
-| `--headless`        | Run test without opening a browser window (useful for CI/CD environments)                  |
 | `--new`             | Create a new sandbox environment for the test run.                                         |
 | `--summary=<value>` | Output file where AI summary should be saved.                                              |
-| `--junit=<value>`   | Output file where junit report should be saved.                                              |
+| `--junit=<value>`   | Output file where junit report should be saved.                                            |
 
 ## Example usage
 

package/docs/docs.json

@@ -103,6 +103,7 @@
               "/guide/authentication",
               "/guide/variables",
               "/guide/lifecycle",
+              "/guide/dashcam",
               "/guide/environment-variables",
               "/action/ami"
             ]

package/docs/getting-started/playwright.mdx

@@ -50,8 +50,9 @@ test.describe("get started link", () => {
     You will need a [Free TestDriver Account](https://app.testdriver.ai/team) to get an API key.
 
     <Card title="Sign Up for TestDriver" icon="user-plus" horizontal href="https://app.testdriver.ai/team">
-      
+
     </Card>
+
   </Step>
   <Step title="Set up your environment">
     Copy your API key from [the TestDriver dashboard](https://app.testdriver.ai/team), and set it as an environment variable.
@@ -68,6 +69,7 @@ test.describe("get started link", () => {
         ```
       </Tab>
     </Tabs>
+
   </Step>
 </Steps>
 
@@ -131,6 +133,7 @@ test.describe("get started link", () => {
         ```
       </Tab>
     </Tabs>
+
   </Step>
 </Steps>
 
@@ -157,6 +160,7 @@ test.describe("get started link", () => {
         ```
       </Tab>
     </Tabs>
+
   </Step>
   <Step title="Run Playwright">
     Before we start using TestDriver in our tests, run Playwright in [UI Mode](https://playwright.dev/docs/test-ui-mode):
@@ -182,6 +186,7 @@ test.describe("get started link", () => {
 
     Clicking the ▶️ button should successfully run the tests in the UI,
     just as they did before with `playwright test` in the CLI.
+
   </Step>
   <Step title="Import TestDriver">
     For the sake of simplicity, we'll be working with one test file for now.
@@ -199,6 +204,7 @@ test.describe("get started link", () => {
     <Tip>
       Click the <Icon icon="eye" /> button to automatically re-run tests on save.
     </Tip>
+
   </Step>
 </Steps>
 
@@ -266,14 +272,15 @@ Now, our test uses natural language to both describe & locate the element.
 <Tip>
   In the example above, you can still use Playwright to assert that the element is indeed a link for accessibility:
 
-  ```typescript tests/example.spec.ts icon=square-js
-  const link = await testdriver(page).locate("Get started link");
-  // [!code ++]
-  expect(link).toHaveRole("link");
-  await link.click();
-  ```
+```typescript tests/example.spec.ts icon=square-js
+const link = await testdriver(page).locate("Get started link");
+// [!code ++]
+expect(link).toHaveRole("link");
+await link.click();
+```
+
+This way you can write user-centric tests _and_ validate the implementation.
 
-  This way you can write user-centric tests _and_ validate the implementation.
 </Tip>
 
 ### Performing actions with `testdriver.act`
@@ -332,4 +339,4 @@ but replaced the `test` itself with `test.agent`.
 
 ## Conclusion
 
-With `@testdriver.ai/playwright`, you can use as much or as little of Playwright's _or_ TestDriver's API as you need to validate correctness. It's up to you!
+With `@testdriver.ai/playwright`, you can use as much or as little of Playwright's _or_ TestDriver's API as you need to validate correctness. It's up to you!

package/docs/getting-started/self-hosting.mdx

@@ -15,28 +15,37 @@ Self-hosting TestDriver allows you to run tests on your own infrastructure, givi
 
 ## Why self host?
 
+Self-hosting TestDriver gives you complete control over your test execution environment:
+
 - **Enhanced security**: Get complete control over ingress and egress rules.
-- **Complete customization**: Modify the TestDriver Golden Image to include custom dependencies, software, and configurations at launch time.
+- **Complete customization**: Modify the TestDriver Golden Image (our pre-configured AMI) to include custom dependencies, software, and configurations at launch time.
 - **Powerful Infrastructure**: Run tests on bare metal infrastructure that support emulators and simulators.
 
+You'll use the [TestDriver CLI repository](https://github.com/testdriverai/cli) which contains all the infrastructure templates and setup scripts needed for self-hosting.
+
 ## Overview
 
-Self-hosting TestDriver gives you complete control over your test execution environment. You'll provision EC2 instances on AWS using our pre-configured AMI and infrastructure templates:
+By the end of this guide, you'll have a complete self-hosted testing infrastructure that can:
+
+- Spawn TestDriver instances on-demand in your AWS account
+- Run tests on your own AWS infrastructure with custom configurations
+- Integrate seamlessly with GitHub Actions CI/CD workflows
+- Automatically clean up resources after test completion
 
-1. **GitHub Workflow**: Use `.github/workflows/self-hosted.yml` as your template to test in CI.
-2. **CloudFormation**: Deploy our `setup/aws/cloudformation.yaml` to provision infrastructure.
-3. **On-Demand Runners**: Use `setup/aws/spawn-runner.sh` with your Launch Template ID from CloudFormation to spawn runners on-demand.
-4. **GitHub Secrets**: Store AWS Credentials to your GitHub repository's secrets.
+The setup process involves three main steps:
+
+1. **CloudFormation Infrastructure**: Deploy our `setup/aws/cloudformation.yaml` template to create the foundational AWS resources (VPC, security groups, IAM roles, and a launch template for instance creation).
+2. **On-Demand Instance Spawning**: Use `setup/aws/spawn-runner.sh` with your Launch Template ID to programmatically spawn TestDriver instances whenever you need to run tests.
+3. **GitHub Actions Integration**: Use `.github/workflows/self-hosted.yml` as a template for running tests in CI. This workflow demonstrates the complete lifecycle: spawning an instance, running tests, and shutting down the instance to minimize costs.
 
 ## Prerequisites
 
 - AWS account with permissions to run CloudFormation.
 - [AWS CLI](https://aws.amazon.com/cli/) installed locally.
 
-  <Tip>
-    Be sure to run `aws configure` with your credentials
-  </Tip>
-- Access to the TestDriver AMI\
+  <Tip>Be sure to run `aws configure` with your credentials</Tip>
+
+- Access to the TestDriver AMI (Golden Image)\
   [Contact us with your preferred AWS Region for access](https://form.typeform.com/to/UECf9rDx?typeform-source=testdriver.ai).
 - A GitHub repository for committing your tests & workflow.
 
@@ -57,7 +66,7 @@ This is a one-time setup used to generate a template ID for launching instances.
 # Deploy the CloudFormation stack
 aws cloudformation deploy \
   --template-file setup/aws/cloudformation.yaml \
-  --stack-name testdriver-infrastructure-11 \
+  --stack-name my-testdriver-infrastructure \
   --parameter-overrides \
     ProjectTag=testdriver \
     AllowedIngressCidr=0.0.0.0/0 \
@@ -67,7 +76,8 @@ aws cloudformation deploy \
 ```
 
 <Danger>
-  **Security**: Replace `AllowedIngressCidr=0.0.0.0/0` with your specific IP ranges to lock down access to your VPC.
+  **Security**: Replace `AllowedIngressCidr=0.0.0.0/0` with your specific IP
+  ranges to lock down access to your VPC.
 </Danger>
 
 ### Get Launch Template ID
@@ -76,32 +86,35 @@ After CloudFormation completes, find the launch template ID in the stack outputs
 
 ```bash
 aws cloudformation describe-stacks \
-  --stack-name testdriver-infrastructure-11 \
+  --stack-name my-testdriver-infrastructure \
   --query 'Stacks[0].Outputs[?OutputKey==`LaunchTemplateId`].OutputValue' \
   --output text
 ```
 
-<Tip>
-  **Save this ID** – you'll need it for the next step.
-</Tip>
+<Tip>**Save this ID** – you'll need it for the next step.</Tip>
 
 ## Step 2: Spawn a New TestDriver Runner
 
-### Using aws-setup.sh
+This step is performed **every time you want to run tests**. The `spawn-runner.sh` script launches a new EC2 instance on-demand for test execution.
 
-Our [`setup/aws/spawn-runner.sh`](https://github.com/testdriverai/cli/tree/main/setup/aws/spawn-runner.sh) spawns and initializes instances:
+### Using spawn-runner.sh
 
-- Launches instances using your launch template
-- Completes TestDriver handshake
-- Returns instance details for CLI usage
+Our [`setup/aws/spawn-runner.sh`](https://github.com/testdriverai/cli/tree/main/setup/aws/spawn-runner.sh) script:
+
+- Launches a new EC2 instance using your launch template from Step 1
+- Waits for the instance to become ready
+- Completes the TestDriver handshake
+- Returns instance details (IP, instance ID) for CLI usage
+
+The script accepts parameters as either environment variables or CLI arguments:
 
 ```bash
-# Launch an instance
+# Launch an instance using environment variables
 export AWS_REGION=us-east-2
 export AMI_ID=ami-••••••••••  # Your TestDriver AMI (contact us to get one)
 export AWS_LAUNCH_TEMPLATE_ID=lt-••••••••••  # From CloudFormation output from step 1
 
-/bin/bash ./setup/aws/aws-setup.sh
+/bin/bash ./setup/aws/spawn-runner.sh
 ```
 
 The script outputs:
@@ -112,6 +125,13 @@ INSTANCE_ID=i-1234567890abcdef0
 AWS_REGION=us-east-2
 ```
 
+<Note>
+  **Instance Lifecycle**: Instances spawned by this script will continue running
+  until you manually terminate them. They are automatically tagged with
+  `Name=TestDriverRunner` and `Project=[your ProjectTag value]` for easy
+  identification in the AWS console.
+</Note>
+
 ### CLI Usage
 
 Once you have an instance IP, run tests directly:
@@ -128,17 +148,26 @@ npx testdriverai@latest run testdriver/your-test.yaml \
   --ip="$PUBLIC_IP" \
 ```
 
-Note that the instance will remain running until you terminate it. You can do this manually via the AWS console, or programmatically in your CI workflow:
+### Terminating Instances
+
+After your tests complete, terminate the instance to avoid unnecessary costs:
 
 ```bash
-aws ec2 terminate-instances --instance-ids $INSTANCE_ID
+# Terminate the instance
+aws ec2 terminate-instances --instance-ids $INSTANCE_ID --region $AWS_REGION
 ```
 
+You can also terminate instances manually through the AWS console by searching for instances tagged with `Name=TestDriverRunner`.
+
 ## Step 3: GitHub Actions Integration
 
+This step shows you how to automate the entire test lifecycle in CI/CD.
+
 ### Example Workflow
 
-Our [`.github/workflows/self-hosted.yml`](https://github.com/testdriverai/cli/tree/main/.github/workflows/self-hosted.yml) demonstrates the complete workflow:
+Our [`.github/workflows/self-hosted.yml`](https://github.com/testdriverai/cli/tree/main/.github/workflows/self-hosted.yml) demonstrates the complete workflow: spawning an EC2 instance, running your tests, and shutting down the instance automatically to minimize costs.
+
+The workflow uses the GitHub secrets you configure (see below) to authenticate with AWS and spawn instances on-demand:
 
 ```yaml
 name: TestDriver Self-Hosted
@@ -205,11 +234,24 @@ Configure these secrets in your GitHub repository:
 
 ### Using the Base AMI
 
-Our AMI comes pre-configured with:
+Our TestDriver Golden Image (AMI) comes pre-configured with everything you need to run tests:
+
+**Operating System & Environment:**
 
 - Windows Server with desktop environment
-- Required TestDriver dependencies
+- VNC + web server for remote desktop access through the browser
+
+**Development Tools:**
+
+- Python (with pip)
+- Node.js (with npm)
+- Git
+
+**Test Infrastructure:**
+
+- TestDriver agent and dependencies
 - Optimized settings for test execution
+- Pre-configured networking for TestDriver CLI communication
 
 ### Modifying the AMI
 
@@ -281,11 +323,13 @@ steps:
 
 ### Common Issues
 
-**Instance not responding:**
+**Instance not responding in TestDriver CLI:**
+
+When the CLI displays connection errors or timeouts, check:
 
-- Check security group rules allow necessary ports
-- Verify instance has passed all status checks
-- Ensure AMI is compatible with selected instance type
+- **Security group rules**: The CloudFormation template configures all necessary ports (RDP 3389, VNC 5900, and TestDriver communication ports). Verify your security group hasn't been modified.
+- **Instance status checks**: Ensure the instance has passed both system and instance status checks in the AWS console.
+- **AMI compatibility**: Verify the AMI is compatible with your selected instance type (some instance types don't support certain AMIs).
 
 **Connection timeouts:**
 
@@ -305,4 +349,4 @@ For enterprise customers:
 
 - Contact your account manager for AMI access issues
 - Use support channels for infrastructure questions
-- Check the TestDriver documentation for CLI usage
+- Check the TestDriver documentation for CLI usage

package/docs/guide/dashcam.mdx

@@ -0,0 +1,118 @@
+---
+title: "Dashcam Replays"
+sidebarTitle: "Dashcam"
+description: "Learn how to use Dashcam to record and replay test sessions in TestDriver."
+icon: "video"
+---
+
+[Dashcam](https://www.dashcam.io), from the makers of TestDriver, is a powerful feature in TestDriver that allows you to record and replay your test sessions. This is particularly useful for debugging, sharing test runs with team members, or reviewing the steps taken during a test. For the full docs see the [Dashcam docs](https://docs.dashcam.io/dashcam/).
+
+## Recording a Test Session
+
+To record a test session, you can use the `dashcam` command in your lifecycle scripts. There are two main lifecycle scripts where you can integrate Dashcam: `lifecycle/prerun.yaml` and `lifecycle/postrun.yaml`.
+
+## Ways to use Dashcam
+
+Dashcam comes as a standalone app and a Chrome extension. You can use either or both to capture your test sessions.
+
+<Info>
+  To capture web logs, make sure to install the Dashcam Chrome extension on the
+  browser you are testing with. We recommend installing it via CLI to Chrome for
+  Testing. You can also find the extension [in the Chrome
+  Webstore](https://chromewebstore.google.com/detail/dashcam/dkcoeknmlfnfimigfagbcjgpokhdcbbp)
+</Info>
+
+### Installing the Dashcam Chrome extension via command line in prerun.yaml
+
+In this lifecycle script, we install Chrome for Testing with a user profile that has the password manager disabled and sets up TestDriver Dashcam for replays and logs.
+
+```yaml lifecycle/prerun.yaml [expandable]
+- prompt: launch chrome for testing and setup dashcam
+    commands:
+      # this script installs chrome for testing with a userprofile that has password manager disabled and sets up TestDriver Dashcam for replays and logs
+      - command: exec
+        lang: pwsh
+        code: |
+          cd $env:TEMP
+          Write-Host "Changed directory to TEMP: $env:TEMP"
+
+          Write-Host "Running 'npm init -y'..."
+          npm init -y
+
+          Write-Host "Installing dependencies: @puppeteer/browsers and dashcam-chrome..."
+          npm install @puppeteer/browsers dashcam-chrome
+
+          Write-Host "Installing Chromium via '@puppeteer/browsers'..."
+          npx @puppeteer/browsers install chrome
+
+          # Define paths
+          $extensionPath = Join-Path (Get-Location) "node_modules/dashcam-chrome/build"
+          $profilePath = Join-Path $env:TEMP "chrome-profile-$(Get-Random)"
+
+          Write-Host "Extension path: $extensionPath"
+          Write-Host "Chrome user data dir: $profilePath"
+
+          # Validate extension path
+          if (-not (Test-Path $extensionPath)) {
+              Write-Host "Extension not found at $extensionPath"
+          }
+
+          $chromeArgs = @(
+            "--start-maximized",
+            "--load-extension=$extensionPath",
+            "--user-data-dir=$profilePath",
+            "--no-first-run",
+            "--no-default-browser-check",
+            "--disable-infobars"
+            "${TD_WEBSITE}"
+          ) -join ' '
+
+          Start-Process "cmd.exe" -ArgumentList "/c", "npx @puppeteer/browsers launch chrome -- $chromeArgs"
+
+          Write-Host "Script complete."
+          exit 0
+```
+
+### Using the Chrome extension and capturing web logs
+
+Now in the same `lifecycle/prerun.yaml` script, we set up Dashcam to track web logs and application logs. You can customize the patterns to match your needs. Testing Desktop? You can skip the web logs and just track application logs.
+
+```yaml lifecycle/prerun.yaml
+...
+- command: exec
+    lang: pwsh
+    code: |
+        dashcam track --name="Web Logs" --type="web" --pattern="*"
+        dashcam track --name=TestDriver --type=application --pattern="C:\Users\testdriver\Documents\testdriver.log"
+```
+
+### Starting Dashcam
+
+The final step in our `lifecycle/prerun.yaml` script is to start Dashcam recording.
+
+```yaml lifecycle/prerun.yaml
+...
+- command: exec
+    lang: pwsh
+    code: dashcam start
+```
+
+### Publishing replays to a project in your account
+
+Lastly, in the `lifecycle/postrun.yaml` script, we publish the recorded Dashcam session to a project in your Dashcam account. Make sure to replace `<YOUR_PROJECT_ID>` with the actual ID of your project.
+
+```yaml lifecycle/postrun.yaml
+- prompt: send dashcam recording to server
+    # this script tells TestDriver Dashcam to send the recording to the server
+  commands:
+    - command: exec
+        lang: pwsh
+        code: dashcam -t '${TD_THIS_FILE}' -p -k <YOUR_PROJECT_ID> # optional add `-k MYFOLDERID` for the id of a folder in your Projects page at app.testdriver.ai
+```
+
+<Info>
+  `${TD_THIS_FILE}` is an environment variable set by TestDriver that contains
+  the name of the current test file being executed. This will be used as the
+  title of the Dashcam recording. For more info see [parallel testing
+  docs](/features/parallel-testing).
+</Info>

package/docs/guide/environment-variables.mdx

@@ -11,13 +11,13 @@ import GitignoreWarning from "/snippets/gitignore-warning.mdx";
 The supported environment variables in TestDriver are:
 
 <div className="env-vars-table">
-  |   Variable      |   Type    | Description                                                                     |
+  | Variable | Type | Description |
   |:---------------:|:---------:|---------------------------------------------------------------------------------|
-  | TD_ANALYTICS    | boolean   | Send analytics to TestDriver servers. This helps provide feedback to inform our roadmap. |
-  | TD_API_KEY      | string    | Set this to spawn VMs with TestDriver Pro.                                        |
+  | TD_ANALYTICS | boolean | Send analytics to TestDriver servers. This helps
+  provide feedback to inform our roadmap. | | TD_API_KEY | string | Set this to
+  spawn VMs with TestDriver Pro. |
 </div>
-  
-<GitignoreWarning/>
+<GitignoreWarning />
 ## Example
 
 ```bash .env

package/docs/overview/comparison.mdx

@@ -10,13 +10,10 @@ icon: boxing-glove
 TestDriver operates a full desktop environment, so it can run any application.
 
 <div className="comparison-table">
-| Application       | TestDriver | Playwright | Selenium |
-|:-----------------:|:---------:|:-----------:|:--------:|
-| Web Apps          | ✅            | ✅       | ✅       |
-| Mobile Apps       | ✅            | ✅       | ✅       |
-| VS Code           | ✅            | ✅       | ✅       |
-| Desktop Apps      | ✅            |          |         |
-| Chrome Extensions | ✅            |          |         |
+  | Application | TestDriver | Playwright | Selenium |
+  |:-----------------:|:---------:|:-----------:|:--------:| | Web Apps | ✅ |
+  ✅ | ✅ | | Mobile Apps | ✅ | ✅ | ✅ | | VS Code | ✅ | ✅ | ✅ | | Desktop
+  Apps | ✅ | | | | Chrome Extensions | ✅ | | |
 </div>
 
 ## Testing features
@@ -24,16 +21,11 @@ TestDriver operates a full desktop environment, so it can run any application.
 TestDriver is AI first.
 
 <div className="comparison-table">
-| Feature               | TestDriver | Playwright | Selenium |
-|:--------------------:|:---------:|:----------:|:--------:|
-| Test Generation       | ✅            |          |        |
-| Adaptive Testing      | ✅            |          |        |
-| Visual Assertions     | ✅            |          |        |
-| Self Healing          | ✅            |          |        |
-| Application Switching | ✅            |          |        |
-| GitHub Actions        | ✅            | ✅       |        |
-| Team Dashboard        | ✅            |          |        |
-| Team Collaboration    | ✅            |          |        |
+  | Feature | TestDriver | Playwright | Selenium |
+  |:--------------------:|:---------:|:----------:|:--------:| | Test Generation
+  | ✅ | | | | Adaptive Testing | ✅ | | | | Visual Assertions | ✅ | | | | Self
+  Healing | ✅ | | | | Application Switching | ✅ | | | | GitHub Actions | ✅ |
+  ✅ | | | Team Dashboard | ✅ | | | | Team Collaboration | ✅ | | |
 </div>
 
 ## Test coverage
@@ -61,15 +53,11 @@ TestDriver has more coverage than selector-based frameworks.
 Debugging features are powered by [Dashcam.io](https://dashcam.io).
 
 <div className="comparison-table">
-| Feature            | TestDriver | Playwright | Selenium |
-|:------------------:|:----------:|:----------:|:--------:|
-| AI Summary         | ✅            |              |        |
-| Video Replay       | ✅            | ✅            |        |
-| Browser Logs       | ✅            | ✅            |        |
-| Desktop Logs       | ✅            |               |        |
-| Network Requests   | ✅            | ✅            |        |
-| Team Dashboard     | ✅            |              |        |
-| Team Collaboration | ✅            |              |        |
+  | Feature | TestDriver | Playwright | Selenium |
+  |:------------------:|:----------:|:----------:|:--------:| | AI Summary | ✅
+  | | | | Video Replay | ✅ | ✅ | | | Browser Logs | ✅ | ✅ | | | Desktop Logs
+  | ✅ | | | | Network Requests | ✅ | ✅ | | | Team Dashboard | ✅ | | | | Team
+  Collaboration | ✅ | | |
 </div>
 
 ## Web browser support
@@ -77,15 +65,10 @@ Debugging features are powered by [Dashcam.io](https://dashcam.io).
 TestDriver is browser agnostic and supports any version of any browser.
 
 <div className="comparison-table">
-| Feature  | TestDriver | Playwright | Selenium |
-|:--------:|:----------:|:----------:|:--------:|
-| Chrome   | ✅            | ✅         | ✅       |
-| Firefox  | ✅            | ✅         | ✅       |
-| Webkit   | ✅            | ✅         | ✅       |
-| IE       | ✅            |            | ✅       |
-| Edge     | ✅            | ✅         | ✅       |
-| Opera    | ✅            |            | ✅       |
-| Safari   | ✅            |            | ✅       |
+  | Feature | TestDriver | Playwright | Selenium |
+  |:--------:|:----------:|:----------:|:--------:| | Chrome | ✅ | ✅ | ✅ | |
+  Firefox | ✅ | ✅ | ✅ | | Webkit | ✅ | ✅ | ✅ | | IE | ✅ | | ✅ | | Edge |
+  ✅ | ✅ | ✅ | | Opera | ✅ | | ✅ | | Safari | ✅ | | ✅ |
 </div>
 
 ## Operating system support
@@ -93,9 +76,7 @@ TestDriver is browser agnostic and supports any version of any browser.
 TestDriver currently supports Mac and Windows!
 
 <div className="comparison-table">
-| Feature  | TestDriver | Playwright | Selenium |
-|:--------:|:----------:|:----------:|:--------:|
-| Windows  | ✅            | ✅       | ✅       |
-| Mac      | ✅            | ✅       | ✅       |
-| Linux    |               | ✅       | ✅       |
+  | Feature | TestDriver | Playwright | Selenium |
+  |:--------:|:----------:|:----------:|:--------:| | Windows | ✅ | ✅ | ✅ | |
+  Mac | ✅ | ✅ | ✅ | | Linux | | ✅ | ✅ |
 </div>

package/docs/overview/quickstart.mdx

@@ -6,7 +6,6 @@ icon: "gauge-high"
 mode: "wide"
 ---
 
-
 <Steps>
   <Step title="Create a TestDriver Account">
       
@@ -78,7 +77,7 @@ mode: "wide"
   </Step>
   <Step title="Run the generated regression test">
 
-    After TestDriver has run the exploratory test, you'll see that the `prompt.yaml` file has been updated with commands generated by the agent to make the test faster and more reliable. 
+    After TestDriver has run the exploratory test, you'll see that the `prompt.yaml` file has been updated with commands generated by the agent to make the test faster and more reliable.
 
     ```yaml
       version: 6.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "testdriverai",
-  "version": "6.1.7",
+  "version": "6.1.8-canary.68bcfa2.0",
   "description": "Next generation autonomous AI agent for end-to-end testing of web & desktop",
   "main": "index.js",
   "bin": {