testdriverai 7.2.63 → 7.2.65

package/testdriver-plugin/skills/running-tests/SKILL.md

@@ -1,77 +0,0 @@
----
-name: running-tests
-description: Run TestDriver tests. Use when executing tests with vitest, debugging test failures, or understanding test output.
----
-
-# Running Tests
-
-Read: `node_modules/testdriverai/docs/v7/running-tests.mdx`
-
-## Basic Commands
-
-```bash
-# Run all tests
-npx vitest run
-
-# Run specific test file
-npx vitest run tests/login.test.mjs
-
-# Run tests matching pattern
-npx vitest run tests/*.test.mjs
-
-# Watch mode (re-runs on file changes)
-npx vitest
-```
-
-## Environment Variables
-
-```bash
-# Required
-TD_API_KEY=your_api_key
-
-# Optional: Run on Windows instead of Linux
-TD_OS=windows
-
-# Optional: AWS config for self-hosted Windows
-AWS_REGION=us-east-2
-AMI_ID=ami-xxxxx
-AWS_LAUNCH_TEMPLATE_ID=lt-xxxxx
-```
-
-## Running with Options
-
-```bash
-# Run specific test with Windows sandbox
-TD_OS=windows npx vitest run tests/example.test.mjs
-
-# Run with increased verbosity
-npx vitest run --reporter=verbose tests/example.test.mjs
-```
-
-## Test Output
-
-TestDriver generates:
-- **Console output**: Real-time test progress
-- **JUnit XML**: `test-report.junit.xml` for CI integration
-- **TestDriver dashboard**: View recordings at [console.testdriver.ai](https://console.testdriver.ai)
-
-## Debugging Failures
-
-1. **Check the recording** - View visual replay on TestDriver dashboard
-2. **Log element info**:
-   ```javascript
-   const el = await testdriver.find("button");
-   console.log("Found:", el.found(), el.confidence, el.text);
-   ```
-3. **Use the two-file workflow** - Iterate quickly with `reconnect: true`
-
-## Two-File Workflow Reminder
-
-For development iteration:
-```bash
-# Step 1: Run setup
-npx vitest run tests/setup.test.mjs
-
-# Step 2: Within 2 minutes, run experiment
-npx vitest run tests/experiment.test.mjs
-```

package/testdriver-plugin/skills/secrets/SKILL.md

@@ -1,87 +0,0 @@
----
-name: secrets
-description: Manage secrets in TestDriver tests. Use when handling passwords, API keys, or sensitive data securely in tests and CI/CD.
----
-
-# Managing Secrets
-
-Read: `node_modules/testdriverai/docs/v7/secrets.mdx`
-
-## Local Development
-
-Use `.env` file (never commit to git):
-
-```bash
-# .env
-TD_API_KEY=td_xxxxxxxxxxxxx
-TEST_PASSWORD=secretpassword123
-STRIPE_TEST_KEY=sk_test_xxxxx
-```
-
-Add to `.gitignore`:
-```
-.env
-.env.local
-```
-
-## Accessing Secrets
-
-```javascript
-const password = process.env.TEST_PASSWORD;
-
-await testdriver.find("Password input").click();
-await testdriver.type(password);
-```
-
-## GitHub Actions Secrets
-
-Add secrets in repository settings (Settings → Secrets → Actions):
-
-```yaml
-# .github/workflows/test.yml
-- name: Run tests
-  env:
-    TD_API_KEY: ${{ secrets.TD_API_KEY }}
-    TEST_PASSWORD: ${{ secrets.TEST_PASSWORD }}
-  run: npx vitest run
-```
-
-## AWS Credentials (for Windows testing)
-
-Required secrets for self-hosted Windows sandboxes:
-
-```yaml
-env:
-  TD_API_KEY: ${{ secrets.TD_API_KEY }}
-  TD_OS: windows
-  AWS_REGION: ${{ secrets.AWS_REGION }}
-  AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
-  AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-  AMI_ID: ${{ secrets.AMI_ID }}
-  AWS_LAUNCH_TEMPLATE_ID: ${{ secrets.AWS_LAUNCH_TEMPLATE_ID }}
-```
-
-## Best Practices
-
-1. **Never hardcode secrets** in test files
-2. **Use `.env.example`** to document required variables:
-   ```bash
-   # .env.example (commit this)
-   TD_API_KEY=
-   TEST_PASSWORD=
-   ```
-3. **Rotate secrets** if accidentally exposed
-4. **Use different credentials** for test vs production
-5. **Limit secret scope** - only expose what's needed
-
-## Masking in Logs
-
-Secrets in environment variables are automatically masked in CI logs. Avoid logging them:
-
-```javascript
-// ❌ Don't do this
-console.log("Password:", process.env.TEST_PASSWORD);
-
-// ✅ Do this
-console.log("Password: [REDACTED]");
-```

package/testdriver-plugin/skills/self-hosting/SKILL.md

@@ -1,89 +0,0 @@
----
-name: self-hosting
-description: Self-host TestDriver sandboxes. Use when running Windows tests on AWS, configuring custom AMIs, or setting up your own infrastructure.
----
-
-# Self-Hosting
-
-Read: `node_modules/testdriverai/docs/v7/self-hosted.mdx`
-Read: `node_modules/testdriverai/docs/v7/aws-setup.mdx`
-
-## When to Self-Host
-
-- **Windows testing** - Required for Windows sandboxes
-- **Custom environments** - Special software or configurations
-- **Data compliance** - Keep tests in your own infrastructure
-- **Performance** - Reduce latency with regional instances
-
-## AWS Setup for Windows
-
-### Prerequisites
-1. AWS account with EC2 access
-2. TestDriver Windows AMI (contact support)
-3. VPC with public subnet
-
-### Required Environment Variables
-
-```bash
-TD_API_KEY=your_api_key
-TD_OS=windows
-AWS_REGION=us-east-2
-AWS_ACCESS_KEY_ID=AKIA...
-AWS_SECRET_ACCESS_KEY=...
-AMI_ID=ami-0dd5fa241273a7d50
-AWS_LAUNCH_TEMPLATE_ID=lt-0ef9bf26a945fb442
-```
-
-### Launch Template Configuration
-
-Create an EC2 launch template with:
-- Instance type: `c5.xlarge` or larger
-- AMI: TestDriver Windows AMI
-- Security group: Allow RDP (3389) and TestDriver ports
-- IAM role: EC2 permissions for your use case
-
-### Running Windows Tests
-
-```bash
-TD_OS=windows npx vitest run tests/windows-app.test.mjs
-```
-
-## Test Configuration
-
-```javascript
-const testdriver = TestDriver(context, {
-  os: 'windows',  // Use Windows sandbox
-});
-
-await testdriver.provision.chrome({ url: 'https://example.com' });
-// or
-await testdriver.provision.installer({
-  url: 'https://example.com/app.msi',
-  launch: true,
-});
-```
-
-## Windows-Specific Examples
-
-- `node_modules/testdriverai/examples/windows-installer.test.mjs`
-- `node_modules/testdriverai/examples/exec-pwsh.test.mjs`
-
-## PowerShell Execution
-
-```javascript
-// Run PowerShell commands on Windows
-const result = await testdriver.exec("pwsh", "Get-Date", 5000);
-const files = await testdriver.exec("pwsh", "Get-ChildItem C:\\", 5000);
-```
-
-## Troubleshooting
-
-**Instance not starting?**
-- Check AWS credentials and permissions
-- Verify launch template exists
-- Check AMI is available in your region
-
-**Connection timeout?**
-- Security group must allow inbound traffic
-- Instance needs public IP or NAT gateway
-- Check TestDriver agent is running on AMI

package/testdriver-plugin/skills/setup/SKILL.md

@@ -1,76 +0,0 @@
----
-name: setup
-description: Set up TestDriver in a project. Use when installing testdriverai, configuring vitest, setting up TD_API_KEY, or initializing a new test project.
----
-
-# Setting Up TestDriver
-
-Read the quickstart guide: `node_modules/testdriverai/docs/v7/quickstart.mdx`
-
-## Requirements
-
-1. **API Key** from [console.testdriver.ai/team](https://console.testdriver.ai/team)
-2. **Node.js** and **Vitest**
-
-## Setup Steps
-
-### 1. Install TestDriver
-
-```bash
-npm install testdriverai vitest dotenv --save-dev
-```
-
-### 2. Create `.env` file
-
-```bash
-TD_API_KEY=your_api_key_here
-```
-
-### 3. Create `vitest.config.mjs`
-
-```javascript
-import { config } from 'dotenv';
-import TestDriver from 'testdriverai/vitest';
-import { defineConfig } from 'vitest/config';
-
-config();
-
-const setupFiles = ['testdriverai/vitest/setup', 'testdriverai/vitest/setup-aws'];
-
-export default defineConfig({
-  test: {
-    testTimeout: 900000,
-    hookTimeout: 900000,
-    disableConsoleIntercept: true,
-    maxConcurrency: 3,
-    reporters: ['default', TestDriver(), ['junit', { outputFile: 'test-report.junit.xml' }]],
-    setupFiles,
-  },
-});
-```
-
-### 4. Add to `.gitignore`
-
-```
-.env
-```
-
-## Verify Setup
-
-Create a test file `tests/example.test.mjs`:
-
-```javascript
-import { describe, expect, it } from "vitest";
-import { TestDriver } from "testdriverai/lib/vitest/hooks.mjs";
-
-describe("Setup Test", () => {
-  it("should load a page", async (context) => {
-    const testdriver = TestDriver(context);
-    await testdriver.provision.chrome({ url: 'https://example.com' });
-    const result = await testdriver.assert("Example Domain heading is visible");
-    expect(result).toBeTruthy();
-  });
-});
-```
-
-Run: `npx vitest run tests/example.test.mjs`

package/testdriver-plugin/skills/variables/SKILL.md

@@ -1,88 +0,0 @@
----
-name: variables
-description: Use variables in TestDriver tests. Use when parameterizing tests, using environment variables, or passing data between test steps.
----
-
-# Using Variables
-
-Read: `node_modules/testdriverai/docs/v7/variables.mdx`
-
-## Environment Variables
-
-Access via `process.env`:
-
-```javascript
-const username = process.env.TEST_USERNAME;
-const password = process.env.TEST_PASSWORD;
-
-await testdriver.find("Username input").click();
-await testdriver.type(username);
-```
-
-## .env File
-
-Create `.env` in project root:
-
-```bash
-TD_API_KEY=your_api_key
-TEST_USERNAME=testuser@example.com
-TEST_PASSWORD=testpass123
-BASE_URL=https://staging.example.com
-```
-
-Load with dotenv (already configured in vitest.config.mjs):
-
-```javascript
-import { config } from 'dotenv';
-config();
-```
-
-## Parameterized Tests
-
-```javascript
-const testCases = [
-  { email: 'user1@test.com', expected: 'Welcome User 1' },
-  { email: 'user2@test.com', expected: 'Welcome User 2' },
-];
-
-describe("Login Tests", () => {
-  testCases.forEach(({ email, expected }) => {
-    it(`should login ${email}`, async (context) => {
-      const testdriver = TestDriver(context);
-      await testdriver.provision.chrome({ url: process.env.BASE_URL });
-      
-      await testdriver.find("Email input").click();
-      await testdriver.type(email);
-      
-      const result = await testdriver.assert(`page shows '${expected}'`);
-      expect(result).toBeTruthy();
-    });
-  });
-});
-```
-
-## Sharing Data Between Steps
-
-```javascript
-it("should complete flow", async (context) => {
-  const testdriver = TestDriver(context);
-  await testdriver.provision.chrome({ url: 'https://example.com' });
-  
-  // Get data from page
-  const orderId = await testdriver.exec("js", 
-    "return document.querySelector('.order-id').textContent", 
-    5000
-  );
-  
-  // Use in later assertions
-  const result = await testdriver.assert(`Order ${orderId} is confirmed`);
-  expect(result).toBeTruthy();
-});
-```
-
-## Dynamic URLs
-
-```javascript
-const baseUrl = process.env.BASE_URL || 'https://localhost:3000';
-await testdriver.provision.chrome({ url: `${baseUrl}/login` });
-```

package/testdriver-plugin/skills/waiting/SKILL.md

@@ -1,72 +0,0 @@
----
-name: waiting
-description: Wait for elements in TestDriver tests. Use when polling for elements, waiting for page loads, handling loading states, or setting timeouts.
----
-
-# Waiting for Elements
-
-Read: `node_modules/testdriverai/docs/v7/waiting-for-elements.mdx`
-
-## Polling with Timeout
-
-Use the `timeout` option to poll until an element is found:
-
-```javascript
-// Retries every 5 seconds until found or timeout
-const element = await testdriver.find("Success message", { timeout: 30000 });
-```
-
-## Wait for Page Load
-
-```javascript
-// Assert something visible after load
-await testdriver.assert("Page has finished loading");
-
-// Or check for specific content
-await testdriver.assert("Welcome message is visible");
-```
-
-## Wait via Assertion
-
-```javascript
-// This will wait and retry until true or timeout
-const loaded = await testdriver.assert("The dashboard has fully loaded");
-expect(loaded).toBeTruthy();
-```
-
-## Wait via exec (JavaScript)
-
-```javascript
-await testdriver.exec("js", `
-  await new Promise(resolve => {
-    const check = () => {
-      if (document.querySelector('.loaded')) resolve();
-      else setTimeout(check, 100);
-    };
-    check();
-  });
-`, 10000);
-```
-
-## Common Patterns
-
-### Wait for element to disappear
-```javascript
-// Keep checking until loading spinner is gone
-let spinner = await testdriver.find("Loading spinner");
-while (spinner.found()) {
-  await new Promise(r => setTimeout(r, 1000));
-  spinner = await testdriver.find("Loading spinner");
-}
-```
-
-### Wait between actions
-```javascript
-await button.click();
-await new Promise(r => setTimeout(r, 2000));  // Wait 2 seconds
-await testdriver.assert("Result is visible");
-```
-
-## Examples
-
-See `node_modules/testdriverai/docs/guide/best-practices-polling.mdx`

package/vitest.config.mjs

@@ -1,29 +0,0 @@
-import { config } from "dotenv";
-import TestDriver from "testdriverai/vitest";
-import { defineConfig } from "vitest/config";
-
-// Load .env file early so it's available to the reporter (runs in main process)
-// and to worker processes
-config();
-
-// Always include AWS setup - it will be a no-op unless TD_OS=windows
-const setupFiles = [
-  "dotenv/config",
-  "testdriverai/vitest/setup",
-  "testdriverai/vitest/setup-aws",
-];
-
-export default defineConfig({
-  test: {
-    testTimeout: 900000,
-    hookTimeout: 900000,
-    disableConsoleIntercept: true,
-    maxConcurrency: 3,
-    reporters: [
-      "default",
-      TestDriver(),
-      ["junit", { outputFile: "test-report.junit.xml" }],
-    ],
-    setupFiles,
-  },
-});