testdriverai 7.2.21 → 7.2.23

package/docs/v7/_drafts/platforms/windows.mdx

@@ -1,430 +0,0 @@
----
-title: "Windows"
-description: "Run TestDriver tests on Windows sandboxes (Enterprise)"
-icon: "windows"
----
-
-<Info>
-Windows sandboxes are available on **Enterprise plans only**. [Contact sales](https://testdriver.ai/contact) to enable Windows testing.
-</Info>
-
-## Overview
-
-Windows sandboxes enable testing of Windows-specific applications, desktop software, and Windows-only workflows.
-
-Windows sandboxes provide:
-- Windows Server 2019/2022
-- Full desktop environment
-- PowerShell and Command Prompt
-- Support for all TestDriver commands
-- Custom AMI support for pre-installed software
-- RDP access for debugging
-
-## Usage
-
-Specify Windows as the operating system:
-
-```javascript
-import { TestDriver } from '@testdriverai/testdriver';
-
-const testdriver = await TestDriver.create({
-  apiKey: process.env.TD_API_KEY,
-  os: 'windows'  // Requires Enterprise plan
-});
-```
-
-### With Lifecycle Helpers
-
-```javascript
-import { chrome } from './setup/lifecycleHelpers.mjs';
-import { test } from 'vitest';
-
-test('windows app test', async (context) => {
-  const { testdriver } = await chrome(context, { 
-    url: 'https://example.com',
-    os: 'windows'
-  });
-  
-  await testdriver.find('login button').then(el => el.click());
-});
-```
-
-## System Details
-
-### Operating System
-- **OS**: Windows Server 2019 or 2022
-- **Architecture**: x86_64 (64-bit)
-- **Desktop**: Windows Desktop Experience
-
-### Pre-installed Software
-- **Browsers**: Chrome, Edge, Firefox
-- **Runtimes**: .NET Framework, .NET Core
-- **Languages**: Node.js, Python (optional)
-- **Tools**: PowerShell 5.1+, Git, Visual Studio Build Tools (optional)
-
-### Default Resolution
-- **1920x1080** (configurable via `resolution` parameter)
-
-## Configuration
-
-### Custom Resolution
-
-Set screen resolution:
-
-```javascript
-const testdriver = await TestDriver.create({
-  apiKey: process.env.TD_API_KEY,
-  os: 'windows',
-  resolution: '1280x720'
-});
-```
-
-### Environment Variables
-
-```javascript
-const testdriver = await TestDriver.create({
-  apiKey: process.env.TD_API_KEY,
-  os: 'windows',
-  env: {
-    NODE_ENV: 'test',
-    DEBUG: 'true'
-  }
-});
-```
-
-## Custom AMI
-
-Enterprise plans support **custom Windows AMIs** with pre-installed software, reducing test setup time.
-
-### Benefits
-- Pre-install proprietary software
-- Configure system settings
-- Install custom certificates
-- Set up development tools
-
-### Setup
-
-1. Contact TestDriver support to create custom AMI
-2. Provide installation scripts and requirements
-3. Reference AMI in tests:
-
-```javascript
-const testdriver = await TestDriver.create({
-  apiKey: process.env.TD_API_KEY,
-  os: 'windows',
-  ami: 'ami-custom-windows-123'  // Your custom AMI ID
-});
-```
-
-See [Self-Hosting Guide](/v7/guides/self-hosting) for details on managing custom AMIs.
-
-## Common Use Cases
-
-### Windows Desktop Applications
-
-Test native Windows applications:
-
-```javascript
-import { test } from 'vitest';
-
-test('windows desktop app', async (context) => {
-  const { testdriver } = await chrome(context, { os: 'windows' });
-  
-  // Launch application
-  await testdriver.exec('pwsh', 
-    'Start-Process "C:\\Program Files\\MyApp\\MyApp.exe"',
-    5000
-  );
-  
-  // Wait for app to load
-  await new Promise(r => setTimeout(r, 3000));
-  
-  // Interact with app
-  await testdriver.find('main menu').then(el => el.click());
-  await testdriver.find('file open').then(el => el.click());
-});
-```
-
-### .NET Applications
-
-Test .NET Framework or .NET Core apps:
-
-```javascript
-test('dotnet app', async (context) => {
-  const { testdriver } = await chrome(context, { os: 'windows' });
-  
-  // Run .NET application
-  await testdriver.exec('pwsh',
-    'dotnet run --project C:\\app\\MyApp.csproj',
-    10000
-  );
-  
-  await testdriver.find('window title').then(el => el.click());
-});
-```
-
-### Registry Operations
-
-Modify Windows Registry:
-
-```javascript
-test('registry test', async (context) => {
-  const { testdriver } = await chrome(context, { os: 'windows' });
-  
-  // Set registry value
-  await testdriver.exec('pwsh',
-    'Set-ItemProperty -Path "HKCU:\\Software\\MyApp" -Name "Setting" -Value "Test"',
-    5000
-  );
-  
-  // Read registry value
-  const result = await testdriver.exec('pwsh',
-    'Get-ItemProperty -Path "HKCU:\\Software\\MyApp" -Name "Setting"',
-    5000
-  );
-  console.log('Registry value:', result);
-});
-```
-
-### File Operations
-
-Work with Windows file system:
-
-```javascript
-test('file operations', async (context) => {
-  const { testdriver } = await chrome(context, { os: 'windows' });
-  
-  // Create directory
-  await testdriver.exec('pwsh', 'New-Item -Path "C:\\Test" -ItemType Directory', 5000);
-  
-  // Download file
-  await testdriver.exec('pwsh',
-    'Invoke-WebRequest -Uri "https://example.com/file.zip" -OutFile "C:\\Test\\file.zip"',
-    30000
-  );
-  
-  // Extract archive
-  await testdriver.exec('pwsh',
-    'Expand-Archive -Path "C:\\Test\\file.zip" -DestinationPath "C:\\Test"',
-    10000
-  );
-});
-```
-
-## Command Execution
-
-### PowerShell
-
-Execute PowerShell commands:
-
-```javascript
-// PowerShell Core (pwsh)
-await testdriver.exec('pwsh', 'Get-Process', 5000);
-
-// PowerShell 5.1 (powershell)
-await testdriver.exec('powershell', 'Get-Service', 5000);
-```
-
-### Command Prompt
-
-Execute CMD commands:
-
-```javascript
-await testdriver.exec('cmd', 'dir C:\\', 5000);
-```
-
-### Batch Scripts
-
-Run batch files:
-
-```javascript
-// Create batch file
-await testdriver.exec('cmd', 
-  'echo @echo off > C:\\test.bat && echo echo Hello >> C:\\test.bat',
-  5000
-);
-
-// Execute batch file
-await testdriver.exec('cmd', 'C:\\test.bat', 5000);
-```
-
-## Package Management
-
-### Chocolatey
-
-Install packages with Chocolatey (if pre-installed on AMI):
-
-```javascript
-// Install package
-await testdriver.exec('pwsh',
-  'choco install -y git',
-  60000
-);
-
-// Use installed software
-await testdriver.exec('pwsh', 'git --version', 5000);
-```
-
-### NPM
-
-Install Node.js packages:
-
-```javascript
-await testdriver.exec('pwsh', 'npm install -g typescript', 30000);
-```
-
-### NuGet
-
-Install .NET packages:
-
-```javascript
-await testdriver.exec('pwsh',
-  'Install-Package Newtonsoft.Json -Force',
-  30000
-);
-```
-
-## Debugging
-
-### RDP Access
-
-Connect via Remote Desktop Protocol:
-
-```javascript
-const instance = testdriver.getInstance();
-console.log('RDP:', `${instance.ip}:${instance.rdpPort || 3389}`);
-
-// Use RDP client to connect and watch tests
-```
-
-### Screenshots
-
-Capture screenshots:
-
-```javascript
-// Windows screenshot via PowerShell
-await testdriver.exec('pwsh',
-  'Add-Type -AssemblyName System.Windows.Forms; [System.Windows.Forms.SendKeys]::SendWait("{PRTSC}"); Start-Sleep -Seconds 1',
-  5000
-);
-```
-
-### Event Logs
-
-Access Windows Event Logs:
-
-```javascript
-const logs = await testdriver.exec('pwsh',
-  'Get-EventLog -LogName Application -Newest 10',
-  5000
-);
-console.log('Event logs:', logs);
-```
-
-## Performance
-
-### Startup Time
-- **First test**: 60-120s (Windows boots slower than Linux)
-- **Subsequent tests**: 0s (sandbox reuse)
-- **Custom AMI**: Faster (pre-installed software)
-
-### Optimization Tips
-- Use custom AMI with pre-installed software
-- Reuse sandboxes across tests
-- Enable caching
-- Minimize software installation during tests
-
-See [Performance Guide](/v7/guides/performance) for details.
-
-## Limitations
-
-### Slower Startup
-Windows sandboxes take longer to boot than Linux (60-120s vs 20-60s).
-
-### Higher Cost
-Windows sandboxes consume more test minutes due to licensing.
-
-### Limited Free Tier
-Windows sandboxes not available on free tier.
-
-## Troubleshooting
-
-### Application Won't Launch
-
-```javascript
-// Try launching with full path
-await testdriver.exec('pwsh',
-  'Start-Process -FilePath "C:\\Program Files\\App\\app.exe"',
-  5000
-);
-
-// Or use cmd
-await testdriver.exec('cmd',
-  'start "" "C:\\Program Files\\App\\app.exe"',
-  5000
-);
-```
-
-### Permission Denied
-
-```javascript
-// Run as administrator (if AMI configured)
-await testdriver.exec('pwsh',
-  'Start-Process -FilePath "app.exe" -Verb RunAs',
-  5000
-);
-```
-
-### Timeout Issues
-
-Increase timeout for slower Windows operations:
-
-```javascript
-await testdriver.exec('pwsh', 'command', 120000);  // 2 minutes
-```
-
-## Enterprise Features
-
-### Custom AMI Management
-- Pre-install proprietary software
-- Configure system settings
-- Install certificates and licenses
-- Set up development environments
-
-### Dedicated Sandboxes
-- Reserved Windows instances
-- Faster startup (always-on)
-- Guaranteed availability
-
-### Support
-- Priority support for Windows issues
-- Custom AMI creation assistance
-- Windows-specific troubleshooting
-
-## Contact Sales
-
-Ready to enable Windows testing?
-
-<Card title="Contact Sales" icon="envelope" href="https://testdriver.ai/contact">
-  Get Enterprise access to Windows sandboxes
-</Card>
-
-## See Also
-
-<CardGroup cols={2}>
-  <Card title="Linux" icon="linux" href="/v7/platforms/linux">
-    Linux sandboxes (default)
-  </Card>
-  
-  <Card title="macOS" icon="apple" href="/v7/platforms/macos">
-    macOS sandboxes (Beta)
-  </Card>
-  
-  <Card title="Self-Hosting" icon="server" href="/v7/guides/self-hosting">
-    Custom AMI management
-  </Card>
-  
-  <Card title="Configuration" icon="gear" href="/v7/getting-started/configuration">
-    Sandbox configuration
-  </Card>
-</CardGroup>

package/docs/v7/_drafts/sdk-logging.mdx

@@ -1,222 +0,0 @@
-# TestDriver SDK - Formatted Logging for Dashcam
-
-The TestDriver SDK now includes clean, structured logging that makes logs easy to read when replayed in Dashcam.
-
-## Features
-
-✨ **Clean, structured formatting** with clear labels and timestamps  
-⏱️ **Timestamp tracking** showing elapsed time from test start  
-🎯 **Action-specific formatting** for find, click, type, hover, scroll, assert  
-⚡ **Cache indicators** showing when elements are found from cache  
-📊 **Test context integration** with Vitest test information  
-🎥 **Dashcam-optimized** - no emojis or ANSI codes, pure text format
-
-## How It Works
-
-All logs sent through the `log:log` event are automatically formatted before being sent to Dashcam. This means when you replay your test in Dashcam, you'll see beautiful, easy-to-read logs with:
-
-- **Clear prefixes** like `[FIND]`, `[CLICK]`, `[ASSERT]` for different action types
-- **Highlighted information** for element descriptions and coordinates
-- **Elapsed timestamps** from test start like `[30.59s]`
-- **Cache hit indicators** showing performance optimizations with `(cached)`
-- **Duration information** for operations
-
-## Usage
-
-### Basic Setup
-
-The formatter is automatically integrated into the SDK. Just use the SDK normally:
-
-```javascript
-import { afterAll, beforeAll, describe, it } from "vitest";
-import {
-  createTestClient,
-  setupTest,
-  teardownTest,
-} from "./setup/testHelpers.mjs";
-
-describe("My Test", () => {
-  let testdriver;
-
-  beforeAll(async () => {
-    testdriver = createTestClient();
-    await setupTest(testdriver);
-  });
-
-  afterAll(async () => {
-    await teardownTest(testdriver);
-  });
-
-  it("should have nice logs", async () => {
-    // Logs are automatically formatted!
-    const button = await testdriver.find("Submit button");
-    await button.click();
-  });
-});
-```
-
-### Enhanced Logging with Test Context
-
-For even better logging with timestamps, set the test context:
-
-```javascript
-beforeAll(async () => {
-  testdriver = createTestClient();
-
-  // Set test context for enhanced logging
-  testdriver.setTestContext({
-    file: "my-test.spec.mjs",
-    test: "My Test Suite",
-    startTime: Date.now(),
-  });
-
-  await setupTest(testdriver);
-});
-```
-
-This enables elapsed time display like `[30.59s]` in your logs.
-
-## Log Format Examples
-
-### Element Found
-
-```
-[30.59s] [FIND] Found "Submit button" at (682, 478) 1597ms (cached)
-```
-
-### Click Action
-
-```
-[35.43s] [CLICK] Click "Submit button"
-```
-
-### Hover Action
-
-```
-[12.15s] [HOVER] Hover "Menu item"
-```
-
-### Type Action
-
-```
-[8.32s] [TYPE] Type "user@example.com"
-```
-
-### Assertion
-
-```
-[42.10s] [ASSERT] "form submission successful" PASSED
-```
-
-### Error
-
-```
-[15.23s] [FAIL] Failed to save debug image - Error: ENOENT: no such file or directory
-```
-
-## Formatter API
-
-The formatter is available through the `sdk-log-formatter.js` module:
-
-```javascript
-const { formatter } = require("./sdk-log-formatter");
-
-// Format different types of messages
-formatter.formatElementFound("Button", {
-  x: 100,
-  y: 200,
-  duration: "1500ms",
-  cacheHit: true,
-});
-formatter.formatAction("click", "Submit button");
-formatter.formatAssertion("form is visible", true);
-formatter.formatError("Connection failed", error);
-```
-
-### Available Methods
-
-- `formatElementFound(description, meta)` - Format element discovery
-- `formatAction(action, description, meta)` - Format user actions
-- `formatAssertion(assertion, passed, meta)` - Format test assertions
-- `formatError(message, error)` - Format error messages
-- `formatHeader(title)` - Create section headers
-- `formatSummary(stats)` - Format test summaries
-- `setTestContext(context)` - Update test context for timing
-
-## Dashcam Compatibility
-
-The formatter is designed specifically for Dashcam replay compatibility:
-
-- **No emojis** - Uses text labels like `[FIND]`, `[CLICK]` instead of icons
-- **No ANSI colors** - Plain text formatting that displays correctly in all environments
-- **No special characters** - Simple ASCII characters only
-- **Clean structure** - Easy to read in logs without terminal formatting
-
-## Integration with Dashcam
-
-When you run tests with Dashcam recording:
-
-1. The SDK sends formatted logs to the `log:log` event
-2. These logs are forwarded to the sandbox via `_forwardLogToSandbox()`
-3. Dashcam captures and stores these logs with precise timestamps
-4. When you replay in Dashcam, you see beautifully formatted logs synchronized with the video
-
-### Example Workflow
-
-```bash
-# Run tests with Dashcam
-npx vitest run testdriver/acceptance-sdk/formatted-logging.test.mjs
-
-# View the replay with formatted logs
-# Open the Dashcam URL from the test output
-```
-
-## Customization
-
-### Custom Action Types
-
-Add custom action types to the formatter:
-
-```javascript
-// In sdk-log-formatter.js, add to getPrefix():
-const prefixes = {
-  // ...existing prefixes
-  myAction: "[CUSTOM]",
-};
-```
-
-### Custom Message Formatting
-
-Override the `formatMessage` method for custom text highlighting:
-
-```javascript
-formatMessage(type, message) {
-  // Add custom highlighting
-  message = message.replace(/\[custom\]/g, chalk.green('[custom]'));
-  return super.formatMessage(type, message);
-}
-```
-
-## Examples
-
-See `testdriver/acceptance-sdk/formatted-logging.test.mjs` for a complete example.
-
-## Benefits for Dashcam Replay
-
-- **Better debugging**: Quickly identify what happened at each step
-- **Professional appearance**: Share polished test recordings with stakeholders
-- **Faster analysis**: Labeled actions make it easy to scan logs
-- **Context awareness**: Timestamps help correlate logs with video timeline
-- **Performance insights**: Cache indicators show optimization opportunities
-- **Universal compatibility**: Works in any environment without terminal support
-
-## Technical Details
-
-The formatter uses:
-
-- **Plain text formatting** for universal compatibility
-- **Event emitters** to intercept log events
-- **Base64 encoding** for safe transmission to sandbox
-- **Test context** from Vitest for timing information
-
-Logs are sent through the existing `log:log` event system, ensuring compatibility with all existing TestDriver infrastructure.

package/test/testdriver/setup/globalTeardown.mjs

@@ -1,11 +0,0 @@
-/**
- * Vitest Global Teardown
- * Saves test results and dashcam URLs after all tests complete
- */
-
-import { saveTestResults } from "./testHelpers.mjs";
-
-export default async function globalTeardown() {
-  console.log("\n🎬 Saving test results and dashcam URLs...");
-  saveTestResults();
-}