testdriverai 7.2.34 → 7.2.36

package/docs/v7/aws-setup.mdx

@@ -13,6 +13,18 @@ graph LR
     B <--> C[Your AWS EC2 Instance]
 ```
 
+# Quickstart
+
+<Card 
+  title="Launch Stack" 
+  icon="aws" 
+  href="https://console.aws.amazon.com/cloudformation/home#/stacks/create/review?templateURL=https://v7-cloudformation-template.s3.us-east-2.amazonaws.com/cloudformation.yaml" 
+  horizontal 
+  arrow
+>
+  Deploy TestDriver infrastructure with one click
+</Card>
+
 ## Overview
 
 The setup process involves three main steps:
@@ -21,6 +33,7 @@ The setup process involves three main steps:
 2. **On-Demand Instance Spawning** — Use `spawn-runner.sh` to launch TestDriver instances when you need to run tests
 3. **CI/CD Integration** — Automate the lifecycle in GitHub Actions: spawn instance → run tests → terminate instance
 
+
 ## Prerequisites
 
 Before you begin, ensure you have:
@@ -31,7 +44,7 @@ Before you begin, ensure you have:
 - A GitHub repository for your tests
 
 <Tip>
-  The TestDriver Golden Image AMI ID is `ami-086b5b4b86d78987c`. Contact us to get access in your preferred AWS region.
+  The TestDriver Golden Image AMI ID is `ami-0504bf50fad62f312`. Contact us to get access in your preferred AWS region.
 </Tip>
 
 ## Step 1: Deploy CloudFormation Stack
@@ -43,57 +56,88 @@ Our CloudFormation template creates all the AWS infrastructure you need:
 - IAM roles and instance profiles
 - EC2 launch template for instance creation
 
-Download the template from the [TestDriver CLI repository](https://github.com/testdriverai/testdriverai/tree/main/setup/aws/cloudformation.yaml), then deploy:
-
-```bash
-aws cloudformation deploy \
-  --template-file setup/aws/cloudformation.yaml \
-  --stack-name testdriver-infrastructure \
-  --parameter-overrides \
-    ProjectTag=testdriver \
-    AllowedIngressCidr=0.0.0.0/0 \
-    InstanceType=c5.xlarge \
-    CreateKeyPair=true \
-  --capabilities CAPABILITY_IAM
-```
+<Tabs>
+  <Tab title="GUI">
+    Click the button below to launch the CloudFormation stack in your AWS Console:
+
+    <Card 
+      title="Launch Stack" 
+      icon="aws" 
+      href="https://console.aws.amazon.com/cloudformation/home#/stacks/create/review?templateURL=https://v7-cloudformation-template.s3.us-east-2.amazonaws.com/cloudformation.yaml" 
+      horizontal 
+      arrow
+    >
+      Deploy TestDriver infrastructure with one click
+    </Card>
+
+    Configure the stack parameters:
+    - **Stack name**: `testdriver-infrastructure` (or your preferred name)
+    - **ProjectTag**: `testdriver`
+    - **AllowedIngressCidr**: Your IP range (e.g., `203.0.113.0/24`)
+    - **InstanceType**: `c5.xlarge` (recommended)
+    - **CreateKeyPair**: `true`
+
+    <Warning>
+      **Security**: Replace `AllowedIngressCidr` with your specific IP ranges to restrict VPC access. Avoid using `0.0.0.0/0` in production.
+    </Warning>
+
+    ### Get Your Launch Template ID
+
+    After the stack creation completes, navigate to the **Outputs** tab to find your `LaunchTemplateId`:
+
+    ![Launch Template ID](/images/content/self-hosted/launchtemplateid.png)
+
+    <Tip>
+      **Save this ID** — you'll need it for spawning instances and CI configuration.
+    </Tip>
+  </Tab>
+  <Tab title="CLI">
+    Download the template from the [TestDriver CLI repository](https://github.com/testdriverai/testdriverai/blob/main/setup/aws/cloudformation.yaml), then deploy:
+
+    ```bash
+    aws cloudformation deploy \
+      --template-file setup/aws/cloudformation.yaml \
+      --stack-name testdriver-infrastructure \
+      --parameter-overrides \
+        ProjectTag=testdriver \
+        AllowedIngressCidr=0.0.0.0/0 \
+        InstanceType=c5.xlarge \
+        CreateKeyPair=true \
+      --capabilities CAPABILITY_IAM
+    ```
 
-<Warning>
-  **Security**: Replace `AllowedIngressCidr=0.0.0.0/0` with your specific IP ranges to restrict VPC access.
-</Warning>
+    <Warning>
+      **Security**: Replace `AllowedIngressCidr=0.0.0.0/0` with your specific IP ranges to restrict VPC access.
+    </Warning>
 
-### Get Your Launch Template ID
+    ### Get Your Launch Template ID
 
-After deployment completes, retrieve the launch template ID:
+    After deployment completes, retrieve the launch template ID:
 
-```bash
-aws cloudformation describe-stacks \
-  --stack-name testdriver-infrastructure \
-  --query 'Stacks[0].Outputs[?OutputKey==`LaunchTemplateId`].OutputValue' \
-  --output text
-```
+    ```bash
+    aws cloudformation describe-stacks \
+      --stack-name testdriver-infrastructure \
+      --query 'Stacks[0].Outputs[?OutputKey==`LaunchTemplateId`].OutputValue' \
+      --output text
+    ```
 
-<Tip>
-  **Save this ID** — you'll need it for spawning instances and CI configuration.
-</Tip>
+    <Tip>
+      **Save this ID** — you'll need it for spawning instances and CI configuration.
+    </Tip>
+  </Tab>
+</Tabs>
 
 ## Step 2: Spawn Test Instances
 
-Use the `spawn-runner.sh` script to launch instances on-demand. This script:
+Use the [`spawn-runner.sh`](https://github.com/testdriverai/testdriverai/blob/main/setup/aws/spawn-runner.sh) script to launch instances on-demand. This script:
 
 - Launches a new EC2 instance using your launch template
 - Waits for the instance to be ready
-- Completes the TestDriver handshake
+- Validates SSM connectivity
 - Returns instance details for test execution
 
 ```bash
-# Set environment variables
-export AWS_REGION=us-east-2
-export AMI_ID=ami-086b5b4b86d78987c
-export AWS_LAUNCH_TEMPLATE_ID=lt-your-template-id
-export RESOLUTION=1440x900  # Optional, default is 1440x900
-
-# Spawn an instance
-./setup/aws/spawn-runner.sh
+AWS_REGION=us-east-2 AMI_ID=ami-0504bf50fad62f312 AWS_LAUNCH_TEMPLATE_ID=lt-your-template-id sh setup/aws/spawn-runner.sh
 ```
 
 Output:
@@ -105,10 +149,28 @@ AWS_REGION=us-east-2
 
 ### Run Tests Against Your Instance
 
-With Vitest, specify the instance IP using the `TD_VM` environment variable:
+Specify the instance IP using the `TD_IP` environment variable:
 
 ```bash
-TD_API_KEY=your-api-key TD_VM=1.2.3.4 npx vitest run
+TD_API_KEY=your-api-key TD_IP=1.2.3.4 npx vitest run
+```
+
+In your test file, pass the IP to TestDriver:
+
+```javascript
+import { describe, it } from "vitest";
+import { TestDriver } from "testdriverai/lib/vitest/hooks.mjs";
+
+describe("My Test", () => {
+  it("should run on self-hosted instance", async (context) => {
+    const testdriver = TestDriver(context, {
+      ip: process.env.TD_IP,
+    });
+
+    await testdriver.provision.chrome({ url: "https://example.com" });
+    // ... your test steps
+  });
+});
 ```
 
 ### Terminate Instances
@@ -176,7 +238,7 @@ jobs:
         run: npx vitest run
         env:
           TD_API_KEY: ${{ secrets.TD_API_KEY }}
-          TD_VM: ${{ steps.aws-setup.outputs.public-ip }}
+          TD_IP: ${{ steps.aws-setup.outputs.public-ip }}
 
       - name: Shutdown AWS Instance
         if: always()
@@ -198,9 +260,60 @@ jobs:
 | `AWS_SECRET_ACCESS_KEY` | AWS secret key | `wJalrXUtnFEMI/K7MDENG...` |
 | `AWS_REGION` | AWS region | `us-east-2` |
 | `AWS_LAUNCH_TEMPLATE_ID` | From CloudFormation output | `lt-07c53ce8349b958d1` |
-| `AMI_ID` | TestDriver AMI ID | `ami-086b5b4b86d78987c` |
+| `AMI_ID` | TestDriver AMI ID | `ami-0504bf50fad62f312` |
 | `TD_API_KEY` | Your TestDriver API key | From [console.testdriver.ai](https://console.testdriver.ai) |
 
+### Example Workflow
+
+For a complete real-world example with matrix-based test execution and dynamic test file discovery, see the [`self-hosted.yml`](https://github.com/testdriverai/testdriverai/blob/main/setup/aws/self-hosted.yml) workflow in the TestDriver repository.
+
+<Tip>
+  **Local Testing**: You can test your GitHub Actions workflow locally using [nektos/act](https://github.com/nektos/act). The `self-hosted.yml` workflow includes commented lines for installing the AWS CLI when running with `act`.
+</Tip>
+
+## Manual Instance Management
+
+You can manage TestDriver instances manually through the AWS Console or CLI. This is useful for debugging, development, or running tests outside of CI/CD.
+
+### Starting an Instance
+
+```bash
+aws ec2 run-instances \
+  --region us-east-2 \
+  --image-id ami-0504bf50fad62f312 \
+  --launch-template LaunchTemplateId=lt-your-template-id \
+  --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=testdriver-manual}]'
+```
+
+### Stopping an Instance
+
+```bash
+aws ec2 stop-instances --region us-east-2 --instance-ids i-1234567890abcdef0
+```
+
+### Starting a Stopped Instance
+
+```bash
+aws ec2 start-instances --region us-east-2 --instance-ids i-1234567890abcdef0
+```
+
+### Terminating Instances
+
+```bash
+aws ec2 terminate-instances --region us-east-2 --instance-ids i-1234567890abcdef0
+```
+
+### Connecting to an Instance
+
+You can connect to running instances via:
+- **RDP** — Use the public IP on port 3389
+- **VNC** — Access via web browser at `http://<public-ip>:5900`
+- **AWS Console** — Use EC2 Instance Connect or Session Manager
+
+<Note>
+  Stopped instances retain their EBS volumes and can be restarted later. Terminated instances are permanently deleted. Always terminate instances when done to avoid storage costs.
+</Note>
+
 ## AMI Customization
 
 The TestDriver Golden Image comes pre-configured with:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "testdriverai",
-  "version": "7.2.34",
+  "version": "7.2.36",
   "description": "Next generation autonomous AI agent for end-to-end testing of web & desktop",
   "main": "sdk.js",
   "exports": {

package/setup/aws/cloudformation.yaml

@@ -81,8 +81,8 @@ Parameters:
 
   CreateKeyPair:
     Type: String
-    AllowedValues: [yes, no]
-    Default: yes
+    AllowedValues: ["yes", "no"]
+    Default: "yes"
     Description: Create a new key pair for instance access? (If 'no', you must provide an existing key name)
   ExistingKeyName:
     Type: String
@@ -168,15 +168,15 @@ Resources:
             IpProtocol: tcp,
             FromPort: 8765,
             ToPort: 8765,
-            CidrIp: 74.220.58.0/24,
-            Description: "pyautogui-cli WebSockets - Static IP 1",
+            CidrIp: 0.0.0.0/0,
+            Description: "pyautogui-cli WebSockets - Open for testing",
           }
         - {
             IpProtocol: tcp,
-            FromPort: 8765,
-            ToPort: 8765,
-            CidrIp: 74.220.50.0/24,
-            Description: "pyautogui-cli WebSockets - Static IP 2",
+            FromPort: 5800,
+            ToPort: 5800,
+            CidrIp: !Ref AllowedIngressCidr,
+            Description: "WebVNC 5800",
           }
         - {
             IpProtocol: tcp,

package/test/testdriver/scroll-keyboard.test.mjs

@@ -30,9 +30,8 @@ describe("Scroll Keyboard Test", () => {
     await testdriver.scroll("down", { amount: 1000 });
 
     // Assert the page is scrolled down
-    const result = await testdriver.assert(
-      "the text 'the hamster dance' is not visible on the webpage",
-    );
+    const result = await testdriver.assert("the page is scrolled down, the hamster dance h1 text heading is not visible on the webpage");
+
     expect(result).toBeTruthy();
   });
 });

package/examples/github-comment-demo.test.mjs

@@ -1,42 +0,0 @@
-/**
- * Example test demonstrating GitHub comment integration
- * 
- * When run in CI with proper environment variables set, this will:
- * 1. Run the tests
- * 2. Record dashcam replays
- * 3. Post a beautiful GitHub comment with results
- */
-
-import { describe, expect, it } from "vitest";
-import { TestDriver } from "../lib/vitest/hooks.mjs";
-
-describe("GitHub Comment Demo", () => {
-  it("should pass with dashcam replay", async (context) => {
-    const testdriver = TestDriver(context, { headless: true });
-    
-    await testdriver.provision.chrome({
-      url: 'https://www.example.com',
-    });
-
-    const heading = await testdriver.find("heading with Example Domain");
-    const result = await testdriver.assert("I can see 'Example Domain' heading");
-    expect(result).toBeTruthy();
-  });
-
-  it("should demonstrate failure handling", async (context) => {
-    const testdriver = TestDriver(context, { headless: true });
-    
-    await testdriver.provision.chrome({
-      url: 'https://www.example.com',
-    });
-
-    // This will fail intentionally to show error reporting
-    const result = await testdriver.assert("I can see a navigation menu with 20 items");
-    expect(result).toBeTruthy(); // This will fail
-  });
-
-  it("should skip when needed", async (context) => {
-    // Skipped tests show in the summary
-    context.skip();
-  });
-});

package/test/manual/reconnect-signin.test.mjs

@@ -1,41 +0,0 @@
-/**
- * TestDriver SDK - Reconnect Test Part 2: Sign In
- * 
- * This test reconnects to the sandbox provisioned by reconnect-provision.test.mjs
- * and clicks the Sign In button.
- * 
- * IMPORTANT: Run this within 2 minutes of reconnect-provision.test.mjs completing.
- * The sandbox auto-terminates after the keepAlive TTL (default 2 minutes).
- * 
- * Usage:
- *   1. npm test -- test/testdriver/reconnect-provision.test.mjs
- *   2. (within 2 minutes) npm test -- test/testdriver/reconnect-signin.test.mjs
- */
-
-import { describe, expect, it } from "vitest";
-import { TestDriver } from "../../lib/vitest/hooks.mjs";
-
-describe("Reconnect Test - Part 2: Sign In", () => {
-
-  it("should reconnect to existing sandbox and click Sign In", async (context) => {
-
-    const testdriver = TestDriver(context, { newSandbox: true, headless: false, reconnect: true });
-    
-    // Provision Chrome and navigate to login page
-    await testdriver.provision.chrome({
-      url: 'http://testdriver-sandbox.vercel.app/login',
-    });
-
-    // Click on Sign In button - the page should already be loaded from provision test
-    const signInButton = await testdriver.find(
-      "Sign In, black button below the password field",
-    );
-    await signInButton.click();
-
-    // Assert that an error shows that fields are required
-    const result = await testdriver.assert(
-      "an error shows that fields are required",
-    );
-    expect(result).toBeTruthy();
-  });
-});