testdriverai 6.0.15 → 6.0.16-canary.e337e67.0

package/agent/index.js

@@ -447,13 +447,14 @@ class TestDriverAgent extends EventEmitter2 {
         sourcePosition: sourcePosition,
       });
 
-      return await this.haveAIResolveError(
+      await this.haveAIResolveError(
         error,
         yaml.dump({ commands: [yml] }),
         depth,
         true,
         shouldSave,
       );
+      throw error;
     }
   }
 

package/docs/account/enterprise.mdx

@@ -7,95 +7,108 @@ icon: gem
 
 import { calendar } from "/snippets/calendar-link.mdx";
 
-We understand that QA coverage is critical and often needed immediately. That's why we're offering our **4x4 Guarantee**: try TestDriver Enterprise and we guarantee you will see 4 tests in your first 4 weeks!
+TestDriver Enterprise is designed for fast-moving teams that need comprehensive QA coverage for complex applications. Our **4x4 Guarantee** ensures you get 4 custom tests created specifically for your application within your first 4 weeks.
 
-Unlike other QA services that take months and cost hundreds of thousands of dollars, TestDriver gets you up and running in just 30 days.
+We specialize in testing scenarios that other tools can't handle - desktop applications, browser extensions, multi-platform workflows, and complex integrations that require custom infrastructure and expert support.
 
 <Card
-  title="Book a Call"
+  title="Schedule a Consultation"
   icon="calendar"
   href="https://calendly.com/d/cq23-qyn-3v6/testdriver-ai-demo"
   link
 >
-  Don't miss out on the cutting-edge of AI and QA testing!
+  Discuss your testing requirements and custom infrastructure needs.
 </Card>
 
 ---
 
-## Pricing
+## Enterprise Plans
 
-We're confident you'll love TestDriver, which is why we're offering this risk-free trial. After the trial, plans start at just **$995/month**, which includes:
+TestDriver Enterprise plans start at **$995/month** and include:
 
-- **12,500 runner minutes per month**: Enough to run 30 tests **2-5 times per day**.
-- Full access to our enterprise test dashboards.
-- Seamless integration with any CI/CD pipeline.
+- **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 more details or to get a demo [Contract Details](#contract-details). To see other plans and pricing, check out our [Pricing](/account/pricing).
+For detailed pricing and contract information, see [Contract Details](#contract-details). For other plans, visit our [Pricing](/account/pricing) page.
 
 <CardGroup cols={3}>
-  <Card title="Quickly Deploy AI QA Tests">
-    Safeguard your most important user flows with generated tests.
+  <Card title="Custom Desktop & Extension Testing">
+    Test complex desktop applications and browser extensions that other tools
+    can't handle.
   </Card>
-  <Card title="Increase Your Total Coverage">
-    Test flows never possible before with our powerful computer-use agent.
+  <Card title="Multi-App Workflow Testing">
+    Test sophisticated workflows that span multiple applications and platforms.
   </Card>
-  <Card title="Spend Less Time on Maintenance">
-    TestDriver tests automatically repair themselves.
+  <Card title="Enterprise Infrastructure & Support">
+    Get dedicated infrastructure and expert support for your unique testing
+    challenges.
   </Card>
 </CardGroup>
 
-## Promotion details
+## Enterprise Features
 
-Here's what's included in all Enterprise plans:
+TestDriver Enterprise provides comprehensive support for fast-moving teams with complex testing requirements:
 
-- **Test Coverage**: Test any publicly available desktop app, Chrome extension, mobile app, or website.
-- **AI-Generated Tests**: Choose from **250 AI-generated tests** within the first 7 days.
-- **Parallel Testing**: No limits on parallel testing.
-- **Daily Test Runs**: Run tests **3-5 times every day**.
-- **AI Quality Reports**: Receive detailed reports delivered directly to your email.
-- **Self-Healing Tests**: AI automatically fixes and maintains your tests.
-- **CI/CD Integration**: Seamlessly integrate with your CI/CD pipeline.
-- **Enterprise Dashboards**: Gain full access to our enterprise-grade test dashboards.
+- **Complex Application Support**: Full testing capabilities for desktop applications, Chrome extensions, mobile apps, and web applications that require specialized infrastructure.
+- **4x4 Custom Test Creation**: Our expert team creates 4 fully customized tests tailored to your specific application and workflows within the first 4 weeks.
+- **Multi-Platform Workflows**: Test complex scenarios spanning multiple applications, browsers, and operating systems.
+- **Unlimited Parallel Testing**: Scale your testing across custom infrastructure without limitations.
+- **Continuous Test Execution**: Automated test runs integrated with your development and deployment cycles.
+- **Intelligent Reporting**: Detailed analytics and quality reports delivered to your team.
+- **Self-Healing Test Maintenance**: AI-powered test maintenance that adapts to application changes.
+- **Custom CI/CD Integration**: Tailored integration with your existing development pipeline.
+- **Enterprise Dashboards**: Advanced analytics and monitoring with custom metrics and insights.
+- **Dedicated Infrastructure**: Specialized testing environments configured for your application stack.
+- **Expert Support**: Ongoing technical support and consultation from our testing specialists.
+
+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).
 
 ---
 
-## How does it work?
+## 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.
 
-1. **Book an Onboarding Call**: Share the specific flows you want to test.
-2. **Generate a Test Suite**: We'll explore your app and generate hundreds of tests using our AI.
-3. **Deploy Tests**: Your new tests will be deployed to your CI/CD pipeline.
-4. **Custom Test Creation**: Our support team will work with you to create tests for any features TestDriver might have missed.
-5. **Engineer Training**: We'll train your engineers on best practices for creating and maintaining TestDriver tests.
+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.
 
 ---
 
-## Onboarding process
+## Implementation Timeline
 
-| Service                  | Timeline      | Description                                                                                   |
-| ------------------------ | ------------- | --------------------------------------------------------------------------------------------- |
-| **Custom Onboarding**    | First 7 Days  | Get set up quickly with custom workflows and Prerun Scripts developed by the TestDriver team. |
-| **AI Test Generation**   | First 7 Days  | Instant coverage: We'll generate hundreds of tests for you to choose from.                    |
-| **Custom Test Creation** | First 30 Days | Our team will create 4 tests for any features TestDriver might have missed.                   |
-| **Training**             | First 30 Days | Our support team will train your engineers on best practices.                                 |
-| **Test Execution**       | Recurring     | Seamless deployment: Tests are executed on a schedule or via CI/CD.                           |
+| 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.                 |
+| **Continuous Execution**          | Ongoing       | Automated test execution with specialized monitoring, reporting, and maintenance.                |
 
 ---
 
-## Contract details
+## Contract Information
 
-- **Free Trial**: Get 30 custom tests free during a 30-day trial when subscribing to the $995/month plan.
-- **Ownership**: The tests are yours! You can modify, duplicate, or distribute them however you wish.
-- **Payment**: A payment method is required to begin the trial.
-- **Renewal**: The contract renews annually. You can pay monthly or annually.
-- **Cancellation**: Cancel anytime during your trial, for any reason.
-- **Credits**: Unused credits don't roll over and expire at the end of each month.
-- **Additional Usage**: Additional usage is billed at standard rates.
-- **On Prem/BYOC**: Option available as an add-on to your contract.
+- **4x4 Guarantee**: 4 custom tests delivered within your first 4 weeks of service.
+- **Test Ownership**: Complete ownership of all tests - modify, duplicate, or distribute as needed.
+- **Payment Terms**: Monthly or annual billing options available.
+- **Contract Term**: Annual contracts with flexible payment schedules.
+- **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.
 
 ---
 
-## Ready to get started?
+## Get Started
 
-Don't wait! <a href={calendar}>**Schedule your onboarding call now**</a> and let us help you achieve QA coverage in just 30 days.
+<a href={calendar}>**Schedule a consultation**</a> to discuss your testing
+requirements and learn how TestDriver Enterprise can support your team's
+development process.

package/docs/action/performance.mdx

@@ -23,9 +23,9 @@ Parallel testing allows you to split your test actions into multiple files and r
 - Use a test matrix strategy to execute these files in parallel.
 
 <Warning>
-  The `run` command is used in your test files to run other test files. This is
-  useful for breaking down large tests into smaller, more manageable pieces. To
-  run multiple separate tests, use a test matrix strategy.
+  The [`run`](/commands/run) command is used in your test files to run other
+  test files. This is useful for breaking down large tests into smaller, more
+  manageable pieces. To run multiple separate tests, use a test matrix strategy.
 </Warning>
 
 Example:
@@ -43,12 +43,12 @@ strategy:
 
 ### 2. Use optimized matching methods
 
-For actions like `hover-text`, `wait-for-text`, and `scroll-until-text`, use the `turbo` matching method instead of `ai`. The `turbo` method uses text similarity to quickly compute the most relevant match, making it about 40% faster than the `ai` method.
+For actions like [`hover-text`](/commands/hover-text), [`wait-for-text`](/commands/wait-for-text), and [`scroll-until-text`](/commands/scroll-until-text), use the `turbo` matching method instead of `ai`. The `turbo` method uses text similarity to quickly compute the most relevant match, making it about 40% faster than the `ai` method.
 
 #### Example
 
 ```yaml
-command: hover-text
+command: [`hover-text`](/commands/hover-text)
 text: Sign In
 description: login button
 action: click
@@ -59,12 +59,12 @@ method: turbo
 
 ### 3. Use `async` asserts
 
-The `assert` command supports the `async: true` property, allowing you to create non-blocking assertions. This means your tests can continue running while the assertion is being validated, saving valuable time.
+The [`assert`](/commands/assert) command supports the `async: true` property, allowing you to create non-blocking assertions. This means your tests can continue running while the assertion is being validated, saving valuable time.
 
 #### Example
 
 ```yaml
-command: assert
+command: [`assert`](/commands/assert)
 expect: The user is logged in
 async: true
 ```

package/docs/commands/hover-text.mdx

@@ -1,3 +1,10 @@
+---
+title: "hover-text"
+sidebarTitle: "hover-text"
+description: "Hover or click on text elements based on a description."
+icon: "text"
+---
+
 <Replay />
 
 <Example />

package/docs/docs.json

@@ -62,7 +62,6 @@
           {
             "group": "Getting Started",
             "pages": [
-              "/getting-started/setup",
               "/getting-started/vscode",
               "/getting-started/running",
               "/getting-started/ci",
@@ -79,7 +78,8 @@
               "/guide/authentication",
               "/guide/lifecycle",
               "/guide/code",
-              "/guide/environment-variables"
+              "/guide/environment-variables",
+              "/guide/protips"
             ]
           },
           {

package/docs/getting-started/vscode.mdx

@@ -10,7 +10,7 @@ import YmlWarning from "/snippets/yml-warning.mdx";
 <Card
   title="Get the VS Code Extension"
   icon="link"
-  href="/getting-started/vscode"
+  href="https://marketplace.visualstudio.com/items?itemName=testdriver.testdriver"
 >
   Turn your IDE into a powerful computer-use automation tool with our VS Code
   extension.

package/docs/guide/lifecycle.mdx

@@ -5,14 +5,6 @@ description: "Learn how to customize TestDriver execution with lifecycle files f
 icon: "arrows-rotate"
 ---
 
-# Lifecycle Files
-
-TestDriver supports lifecycle files to customize test execution at different phases. These files allow you to define custom setup, provisioning, and cleanup steps that run automatically during test execution.
-
----
-
-## Overview
-
 Lifecycle files are YAML files placed in your repository's `lifecycle/` directory. TestDriver automatically executes these files during the appropriate phases:
 
 - **`lifecycle/provision.yaml`**: Executed when a new sandbox is created

package/docs/guide/protips.mdx

@@ -0,0 +1,42 @@
+---
+title: "Pro Tips"
+sidebarTitle: "Pro Tips"
+description: "Navigate TestDriver like a pro with these tips and tricks."
+icon: "star"
+---
+
+TestDriver is a vision-based testing tool and is not aware of the underlying HTML structure of the page. Pay attention to the following tips to improve your testing experience and reduce test flake.
+
+### Use unique descriptions for `hover-image` and `hover-text`
+
+When executing the `hover-image` and `hover-text` command, TestDriver may use the description to identify the image, especially if multiple images are visible. If multiple images on the screen match the description, TestDriver may not be able to determine which one to interact with. To improve accuracy, use specific and unique descriptions for images.
+
+TestDriver may not accurately locate matches in certain cases. This can lead to unexpected behavior when using the `hover-image` or `hover-text` command. For example, if you specify a description that's too generic or similar to other images on the screen, TestDriver may not be able to identify the correct image to interact with. To improve accuracy, use specific and unique descriptions for images and text.
+When executing the `hover-image` and `hover-text` commands, TestDriver uses the provided description to identify the target image or text. If the description is too generic or matches multiple elements on the screen, TestDriver may not be able to determine which one to interact with, leading to unexpected behavior. To improve accuracy, always use specific and unique descriptions for both images and text.
+### Avoid using `hover-text` for single characters (ex: `1`, `>`, `|`)
+
+To improve accuracy of our model, we do not include single characters or symbols in the matching data. This means that `hover-text` may not work as expected for these cases. If you need to interact with single characters or symbols, consider using the `match-image` command with a screenshot of the target element instead.
+
+### Use `<label>`s to match empty text inputs.
+
+To focus empty text inputs, prefer to `hover-text` on the label associated with the input. This [should](https://www.w3.org/WAI/tutorials/forms/labels/) focus the input field.
+
+This is more reliable than trying to match the empty input itself, which may not have any visible text. You can always use `match-image` to match the input field if needed.
+
+### Provide strict criteria for `assert`
+
+Assertions use the current state of the page to determine if the step passes or fails. `assert` is not aware of the past, so avoid writing "assert" steps that rely on previous state. Instead, use `assert` to check the current state of the page against strict criteria.
+
+## Reporting issues
+
+If you encounter any issues while using TestDriver, please report them to us. You can do this by creating a new issue in the [Feedback Forum](https://forums.testdriver.ai/c/feedback/10). We appreciate your feedback and will work to resolve any problems as quickly as possible.
+
+<Card
+  title="Report an Issue"
+  icon="arrow-turn-down-right"
+  iconType="duotone"
+  horizontal
+  href="https://forums.testdriver.ai/c/feedback/10"
+>
+  We'd love to hear from you!
+</Card>

package/package.json

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

package/testdriver/acceptance/remember.yaml

@@ -1,7 +1,27 @@
-version: 5.7.7
-session: 682f66241f5b5f003ee139cb
+version: 6.0.11
+session: 689a163a8d474e20a6142e70
 steps:
-  - prompt: remember the username of the user who cannot login
+  - prompt: focus chrome, remember the password, enter the username and the remembered password and login
     commands:
-      - command: focus-application
-        name: Google Chrome
+      - command: remember
+        description: the password
+        output: my_password
+      - command: hover-text
+        text: Username
+        description: username input field
+        action: click
+      - command: type
+        text: standard_user
+      - command: press-keys
+        keys:
+          - tab
+      - command: type
+        text: ${OUTPUT.my_password}
+      - command: press-keys
+        keys:
+          - tab
+      - command: press-keys
+        keys:
+          - enter
+      - command: assert
+        expect: the homepage is visible

package/testdriver/examples/web/lifecycle/prerun.yaml

@@ -22,16 +22,33 @@ steps:
 
           # Define paths
           $extensionPath = Join-Path (Get-Location) "node_modules/dashcam-chrome/build"
-          $profilePath = Join-Path $env:TEMP "chrome-profile-$(Get-Random)"
+          $profilePath   = Join-Path $env:TEMP "chrome-profile-$(Get-Random)"
+          $defaultDir    = Join-Path $profilePath "Default"
+          $prefsPath     = Join-Path $defaultDir "Preferences"
 
           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"
-          }
+          # Create a clean profile + Preferences to disable password manager & autofill
+          Remove-Item $profilePath -Recurse -Force -ErrorAction SilentlyContinue
+          New-Item $defaultDir -ItemType Directory -Force | Out-Null
 
+          $prefs = @{
+            "credentials_enable_service" = $false
+            "profile" = @{
+              "password_manager_enabled" = $false
+            }
+            "autofill" = @{
+              "profile_enabled"       = $false
+              "address_enabled"       = $false
+              "credit_card_enabled"   = $false
+            }
+          } | ConvertTo-Json -Depth 6
+
+          # Write Preferences before Chrome starts (ASCII/UTF8 is fine)
+          $prefs | Set-Content -Path $prefsPath -Encoding ASCII
+
+          # Build args
           $chromeArgs = @(
             "--start-maximized",
             "--load-extension=$extensionPath",
@@ -43,9 +60,6 @@ steps:
           ) -join ' '
 
           Start-Process "cmd.exe" -ArgumentList "/c", "npx @puppeteer/browsers launch chrome -- $chromeArgs"
-
-          Write-Host "Script complete."
-          exit
       - command: wait-for-text
         text: ${TD_WEBSITE}
         timeout: 60000

package/docs/commands/issues.mdx

@@ -1,20 +0,0 @@
----
-title: "Known Issues"
-sidebarTitle: "Known Issues"
-description: "Known issues and limitations of TestDriver."
-icon: "bug"
----
-
-## Reporting issues
-
-If you encounter any issues while using TestDriver, please report them to us. You can do this by creating a new issue in our [GitHub repository](https://github.com/testdriverai/testdriverai/issues/new). We appreciate your feedback and will work to resolve any problems as quickly as possible.
-
-## Known issues
-
-### Image description matches
-
-TestDriver may not accurately match image descriptions in certain cases. This can lead to unexpected behavior when using the `hover-image` command. For example, if you specify a description that's too generic or similar to other images on the screen, TestDriver may not be able to identify the correct image to interact with. To improve accuracy, use specific and unique descriptions for images.
-
-### Text substrings
-
-TestDriver may not accurately match text substrings in certain cases. This can lead to unexpected behavior when using the `hover-text` command.

package/docs/docs-future.json.txt

@@ -1,114 +0,0 @@
-
-{
-  "group": "Features",
-  "pages": [
-    "/features/selectorless",
-    "/features/generation",
-    "/features/visual-assertions",
-    "/features/auto-healing",
-    "/features/cross-platform",
-    "/features/reusable-snippets",
-    "/features/parallel-testing",
-    "/features/github"
-  ]
-},
-{
-  "tab": "Examples",
-  "groups": [
-    {
-      "group": "Scenarios",
-      "pages": [
-        "cookie-banner",
-        "log-in",
-        "spell-check",
-        "form-filling",
-        "file-upload",
-        "pdf-generation",
-        "ai-chatbot"
-      ]
-    },
-    {
-      "group": "Apps",
-      "pages": [
-        "static-websites",
-        "chrome-extensions",
-        "mobile-apps",
-        "desktop-apps"
-      ]
-    }]
-},
-{
-  "tab": "Integrations",
-  "groups": [
-    {
-      "group": "Buidling",
-      "pages": [
-        "/integrations/vercel",
-        "/integrations/netlify",
-        "/integrations/electron"
-      ]
-    },
-    {
-      "group": "Importing",
-      "pages": [
-        "/importing/testrail",
-        "/importing/jira",
-        "/importing/gherkin",
-        "/importing/csv"
-      ]
-    },
-    {
-      "group": "Exporting",
-      "pages": [
-        "/exploting/playwright"
-      ]
-    },
-    {
-      "group": "Bug Reporting",
-      "pages": [
-        "/bugs/jira"
-      ]
-    }]
-},
-
-
-
-      {
-        "tab": "Guide",
-        "groups": [
-          {
-            "group": "Getting Started",
-            "pages": [
-              "/getting-started/vscode",
-              "/getting-started/setup",
-              "/getting-started/writing",
-              "/getting-started/generating",
-              "/getting-started/running",
-              "/getting-started/ci"
-            ]
-          },
-          {
-            "group": "Writing Tests",
-            "pages": [
-              "/guide/locating",
-              "/guide/waiting",
-              "/guide/assertions",
-              "/guide/variables",
-              "/guide/authentication",
-              "/guide/setup-teardown",
-              "/guide/code"
-            ]
-          },
-          {
-            "group": "Running in CI",
-            "pages": [
-              "/action/setup",
-              "/action/browser",
-              "/action/os",
-              "/action/output",
-              "/action/performance",
-              "/action/prerun",
-              "/action/secrets"
-            ]
-          }]
-      },

package/docs/support/known-bugs.mdx

@@ -1,85 +0,0 @@
----
-title: macOS Automation Limitations
-description: Understanding the limitations of synthetic input automation on macOS when using tools like robot.js in TestDriver.
----
-
-# macOS Automation Limitations
-
-macOS includes several system-level security features that affect how synthetic input—like mouse clicks and keyboard presses generated by automation tools—is interpreted. If you're using tools like `robot.js` for test automation, it's important to understand which applications and interactions may be blocked or ignored by the system.
-
-## 🔐 System-Level Protected Apps
-
-Some macOS applications are **heavily protected** by System Integrity Protection (SIP) and will **not respond to synthetic input**, even if Accessibility permissions are granted.
-
-Examples include:
-
-- **Finder**
-- **System Settings / System Preferences**
-- **Dock**
-- **Menu Bar**
-- **Login Window**
-- **Launchpad**
-- **Installer**
-- **File Open / Save Dialogs**
-
-These apps typically ignore input generated by tools like `robot.js` or even AppleScript unless scripted via system-sanctioned methods.
-
-<Alert type="warning" title="Heads up">
-Synthetic double-clicks often fail in Finder, even when the correct timing and coordinates are used.
-</Alert>
-
-## 🛡️ TCC-Protected Applications
-
-Apps protected by Transparency, Consent, and Control (TCC) **can be automated** if the right permissions are granted.
-
-To enable automation for these apps:
-
-1. Go to **System Settings > Privacy & Security > Accessibility**
-2. Add and check the app or terminal running your automation (e.g., Terminal, iTerm, VS Code).
-3. You may also need to grant:
-   - **Input Monitoring**
-   - **Screen Recording**
-   - **Full Disk Access**
-
-These permissions allow tools like `robot.js` to simulate clicks, keystrokes, and screen interactions in:
-
-- **Google Chrome**
-- **Safari**
-- **Slack**
-- **Mail**
-- **Calendar**
-- **Notes**
-- **VS Code**
-- **Xcode**
-
-## ⚙️ Best Targets for UI Automation
-
-For reliable automation, use `robot.js` or TestDriver with:
-
-- Chromium-based browsers (Chrome, Brave, Edge)
-- Electron apps (Slack, Discord)
-- Most third-party GUI apps
-- Terminal emulators
-
-These apps typically respect synthetic input when appropriate permissions are granted.
-
-## 🚫 Actions That Can't Be Automated
-
-macOS enforces strict security policies on certain sensitive UI elements. Automation is **not possible** for:
-
-- Login screen interactions
-- Security permission prompts (e.g., “Allow Screen Recording”)
-- Password input in secure dialogs
-- Force Quit window
-- Crash reporter popups
-
-## ✅ Recommendations
-
-- Always **grant Accessibility permissions** to the app or terminal running `robot.js`.
-- Use **AppleScript** for system apps like Finder or System Settings.
-- For GUI testing, prefer apps that are not protected by SIP.
-- Consider using native tools like **XCUITest** or **Appium** for native macOS apps.
-
-<Alert type="info" title="Need Help?">
-If you're running into automation issues in specific apps, reach out on Discord or contact the TestDriver team.
-</Alert>

package/testdriver/examples/doom/.env.example

@@ -1 +0,0 @@
-TD_API_KEY=

package/testdriver/examples/doom/lifecycle/provision.yaml

@@ -1,46 +0,0 @@
-version: 6.0.0
-session: 67f00511acbd9ccac373edf7
-steps:
-  - prompt: download arc browser
-    commands:
-      - command: exec
-        lang: pwsh
-        code: |
-          # === Setup ===
-          $chocoUrl = "https://www.chocolate-doom.org/downloads/3.0.1/chocolate-doom-3.0.1-win32.zip"
-          $wadUrl = "https://archive.org/download/DOOMIWADFILE/DOOM.WAD"
-          $basePath = "$env:USERPROFILE\choco-doom"
-          $extractDir = "$basePath\choco-extracted"
-          $wadFile = "$basePath\DOOM.WAD"
-          $chocoExe = "$extractDir\chocolate-doom.exe"
-          $zipPath = "$basePath\choco.zip"
-
-          # === Ensure clean folders ===
-          New-Item -ItemType Directory -Force -Path $basePath | Out-Null
-          New-Item -ItemType Directory -Force -Path $extractDir | Out-Null
-
-          # === Download Chocolate DOOM if missing ===
-          if (-not (Test-Path $zipPath)) {
-              Write-Host "Downloading Chocolate DOOM..."
-              Invoke-WebRequest -Uri $chocoUrl -OutFile $zipPath
-          }
-
-          # === Extract if not already extracted ===
-          if (-not (Test-Path $chocoExe)) {
-              Write-Host "Extracting Chocolate DOOM..."
-              Expand-Archive -LiteralPath $zipPath -DestinationPath $extractDir -Force
-          }
-
-          # === Download DOOM.WAD if missing ===
-          if (-not (Test-Path $wadFile)) {
-              Write-Host "Downloading DOOM.WAD..."
-              Invoke-WebRequest -Uri $wadUrl -OutFile $wadFile
-          }
-
-          # === Set SDL variables for software rendering ===
-          $env:SDL_VIDEODRIVER = "windows"
-          $env:SDL_RENDER_DRIVER = "software"
-
-          # === Launch DOOM ===
-          Write-Host "Launching Chocolate DOOM with software rendering..."
-          Start-Process -FilePath $chocoExe -ArgumentList "-iwad `"$wadFile`""

package/testdriver/examples/doom/readme.md

@@ -1 +0,0 @@
-Can launch doom, but can not interact with it (probably due to emulation).

package/testdriver/examples/mobile/readme.md

@@ -1,3 +0,0 @@
-# TBD
-
-- Alex is working on this

package/testdriver/examples/npm/lifecycle/prerun.yaml

@@ -1,19 +0,0 @@
-version: 6.0.0
-session: 67f00511acbd9ccac373edf7
-steps:
-  - prompt: download and run npm
-    commands:
-      - command: exec
-        lang: pwsh
-        code: |
-          # Download and install Chocolatey:
-            powershell -c "irm https://community.chocolatey.org/install.ps1|iex"
-
-            # Download and install Node.js:
-            choco install nodejs --version="22.17.1"
-
-            # Verify the Node.js version:
-            node -v # Should print "v22.17.1".
-
-            # Verify npm version:
-            npm -v # Should print "10.9.2".

package/testdriver/examples/performance/lifecycle/prerun.yaml

@@ -1,40 +0,0 @@
-version: 6.0.0
-session: 67f00511acbd9ccac373edf7
-steps:
-  - prompt: download and run npm
-    commands:
-      - command: exec
-        lang: pwsh
-        code: |
-          # Set the output log file path
-          $logFile = "$PSScriptRoot\SystemUsageLog.csv"
-
-          # Write header if the log file does not exist
-          if (!(Test-Path $logFile)) {
-              "Timestamp,CPU_Usage_Percent,Memory_Used_MB,Memory_Total_MB,Memory_Usage_Percent" | Out-File $logFile
-          }
-
-          # Monitor loop
-          while ($true) {
-              $timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
-
-              # Get CPU usage
-              $cpuUsage = Get-Counter '\Processor(_Total)\% Processor Time'
-              $cpuValue = [math]::Round($cpuUsage.CounterSamples.CookedValue, 2)
-
-              # Get memory usage
-              $comp = Get-CimInstance Win32_OperatingSystem
-              $totalMemory = [math]::Round($comp.TotalVisibleMemorySize / 1024, 2)
-              $freeMemory = [math]::Round($comp.FreePhysicalMemory / 1024, 2)
-              $usedMemory = [math]::Round($totalMemory - $freeMemory, 2)
-              $memPercent = [math]::Round(($usedMemory / $totalMemory) * 100, 2)
-
-              # Append log entry
-              "$timestamp,$cpuValue,$usedMemory,$totalMemory,$memPercent" | Out-File -Append -Encoding utf8 $logFile
-
-              # Output to screen (optional)
-              Write-Host "$timestamp | CPU: $cpuValue% | RAM: $usedMemory / $totalMemory MB ($memPercent%)"
-
-              # Wait before next poll
-              Start-Sleep -Seconds 5
-          }

package/testdriver/examples/performance/monitor.yaml

@@ -1,40 +0,0 @@
-version: 6.0.0
-session: 67f00511acbd9ccac373edf7
-steps:
-  - prompt: download and run npm
-    commands:
-      - command: exec
-        lang: pwsh
-        code: |
-          # Set the output log file path
-          $logFile = "$PSScriptRoot\SystemUsageLog.csv"
-
-          # Write header if the log file does not exist
-          if (!(Test-Path $logFile)) {
-              "Timestamp,CPU_Usage_Percent,Memory_Used_MB,Memory_Total_MB,Memory_Usage_Percent" | Out-File $logFile
-          }
-
-          # Monitor loop
-          while ($true) {
-              $timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
-
-              # Get CPU usage
-              $cpuUsage = Get-Counter '\Processor(_Total)\% Processor Time'
-              $cpuValue = [math]::Round($cpuUsage.CounterSamples.CookedValue, 2)
-
-              # Get memory usage
-              $comp = Get-CimInstance Win32_OperatingSystem
-              $totalMemory = [math]::Round($comp.TotalVisibleMemorySize / 1024, 2)
-              $freeMemory = [math]::Round($comp.FreePhysicalMemory / 1024, 2)
-              $usedMemory = [math]::Round($totalMemory - $freeMemory, 2)
-              $memPercent = [math]::Round(($usedMemory / $totalMemory) * 100, 2)
-
-              # Append log entry
-              "$timestamp,$cpuValue,$usedMemory,$totalMemory,$memPercent" | Out-File -Append -Encoding utf8 $logFile
-
-              # Output to screen (optional)
-              Write-Host "$timestamp | CPU: $cpuValue% | RAM: $usedMemory / $totalMemory MB ($memPercent%)"
-
-              # Wait before next poll
-              Start-Sleep -Seconds 5
-          }

package/testdriver/examples/performance/readme.md

@@ -1 +0,0 @@
-Needs `dashcam track` call

package/testdriver/examples/playwright-test-recording/hello-world.yaml

@@ -1,2 +0,0 @@
-steps:
-  - prompt: interact with the webpage

package/testdriver/examples/playwright-test-recording/lifecycle/prerun.yaml

@@ -1,28 +0,0 @@
-version: 6.0.0
-session: 67f00511acbd9ccac373edf7
-steps:
-  - prompt: launch playwright test recorder
-    commands:
-      - command: exec
-        lang: pwsh
-        code: |
-          powershell -c "irm https://community.chocolatey.org/install.ps1|iex"
-
-          # Download and install Node.js:
-          choco install nodejs --version="22.17.1"
-
-          # Verify the Node.js version:
-          node -v # Should print "v22.17.1".
-
-          # Verify npm version:
-          npm -v # Should print "10.9.2".
-
-          echo "Step 3: Installing Playwright dependencies"
-          npx playwright install --with-deps chromium
-
-          echo "Step 4: Generating Playwright script"
-          $process = Start-Process -FilePath "npx" -ArgumentList "playwright codegen --target playwright-test https://airbnb.com" -PassThru
-          Write-Output "Started Playwright with PID: $($process.Id)"
-
-          echo "Step 5: Completed"
-          exit

package/testdriver/examples/playwright-test-recording/readme.md

@@ -1 +0,0 @@
-Worked in v5, `npx` may be failing