testdriverai 5.5.4 → 5.5.6

package/agent.js

@@ -160,7 +160,7 @@ function completer(line) {
     "/summarize /save /run /quit /assert /undo /manual /yml /js /exec".split(
       " ",
     );
-  if (line.startsWith("/run ") || line.startsWith("/explore ")) {
+  if (line.startsWith("/run ")) {
     return fileCompleter(line);
   } else {
     completions.concat(tasks);
@@ -851,9 +851,6 @@ const firstPrompt = async () => {
       let shouldExit = flags.includes("--exit") ? true : false;
 
       await run(file, shouldSave, shouldExit);
-    } else if (input.indexOf("/explore") == 0) {
-      const file = commands[1];
-      await run(file, true, true);
     } else if (input.indexOf("/generate") == 0) {
       const skipYaml = commands[4] === "--skip-yaml";
       await generate(commands[1], commands[2], commands[3], skipYaml);
@@ -882,7 +879,7 @@ const firstPrompt = async () => {
         logger.error(result.error.result.stdout);
       }
     } else {
-      await exploratoryLoop(input, false, true, true);
+      await exploratoryLoop(input.replace(/^\/explore\s+/, ""), false, true, true );
     }
 
     setTerminalWindowTransparency(false);
@@ -1082,12 +1079,10 @@ let run = async (file = thisFile, shouldSave = false, shouldExit = true) => {
   if (ymlObj.version) {
     let valid = isValidVersion(ymlObj.version);
     if (!valid) {
-      logger.error(
-        `Version mismatch: ${file}. Trying to run a test with v${ymlObj.version} test when this package is v${package.version}.`,
-      );
-
-      await summarize("Version mismatch");
-      await exit(true);
+      console.log("")
+      logger.warn(chalk.red(`Version mismatch detected!`));
+      logger.warn(chalk.red(`Running a test created with v${ymlObj.version}.`));
+      logger.warn(chalk.red(`The current testdriverai version is v${package.version}.`));
     }
   }
 
@@ -1210,18 +1205,19 @@ const buildEnv = async () => {
 };
 
 const start = async () => {
-  // logger.info(await  system.getPrimaryDisplay());
-
-  // @todo add-auth
-  // if (!process.env.DASHCAM_API_KEY) {
-  //   log('info', chalk.red(`You must supply an API key`), 'system')
-  //   log('info', `Supply your API key with the \`DASHCAM_API_KEY\` environment variable.`, 'system');
-  //   log('info', 'You can get a key in the Dashcam Discord server: https://discord.com/invite/cWDFW8DzPm', 'system')
-  //   process.exit();
-  // }
 
   let a = getArgs();
 
+  thisFile = a.file;
+  const thisCommand = a.command;
+
+  logger.info(chalk.green(`Howdy! I'm TestDriver v${package.version}`));
+  logger.info(`This is beta software!`);
+  logger.info("");
+  logger.info(chalk.yellow(`Join our Discord for help`));
+  logger.info(`https://discord.com/invite/cWDFW8DzPm`);
+  logger.info("");
+
   // make testdriver directory if it doesn't exist
   let testdriverFolder = path.join(workingDir, "testdriver");
   if (!fs.existsSync(testdriverFolder)) {
@@ -1235,29 +1231,23 @@ const start = async () => {
 
   }
 
-  // if testdriver.yaml doesn't exist, make it
-  let testdriverFile = path.join(testdriverFolder, "testdriver.yaml");
-  if (!fs.existsSync(testdriverFile)) {
-    fs.writeFileSync(testdriverFile, "");
-    logger.info(chalk.dim(`Created testdriver.yaml`));
-    console.log(chalk.dim(`Created testdriver.yaml: ${testdriverFile}`));
+  // if the directory for thisFile doesn't exist, create it
+  const dir = path.dirname(thisFile);
+  if (!fs.existsSync(dir)) {
+    fs.mkdirSync(dir, { recursive: true });
+    logger.info(chalk.dim(`Created directory ${dir}`));
   }
 
-  thisFile = a.file;
-  const thisCommand = a.command;
-
-  logger.info(chalk.green(`Howdy! I'm TestDriver v${package.version}`));
-  logger.info(`This is beta software!`);
-  logger.info("");
-  logger.info(chalk.yellow(`Join our Discord for help`));
-  logger.info(`https://discord.com/invite/cWDFW8DzPm`);
-  logger.info("");
-
-  // individual run ID for this session
-  // let runID = new Date().getTime();
+  // if thisFile doesn't exist, create it
+  if (!fs.existsSync(thisFile)) {
+    fs.writeFileSync(thisFile, "");
+    logger.info(chalk.dim(`Created ${thisFile}`));
+  }
 
+  if (config.TD_API_KEY) {
+    await sdk.auth();
+  }
 
-  // await sdk.auth();
   if (thisCommand !== "run") {
     speak("Howdy! I am TestDriver version " + package.version);
   }

package/docs/account/dashboard.mdx

@@ -0,0 +1,16 @@
+---
+title: "Dashboard"
+sidebarTitle: "Dashboard"
+description: "Explore your TestDriver dashboard and its features."
+icon: "gauge"
+---
+## Welcome to your TestDriver Dashboard
+Your dashboard is your command center for managing your TestDriver experience. Here, you can view your projects, monitor usage, and access various features to enhance your testing workflow.
+
+## Key Features
+- **Projects**: Get a quick snapshot of your projects, with all Dashcam replays.
+- **Team**: Manage your API key, and add/remove team members. 
+- **Usage & Billing**: Monitor your usage and credits in real-time.
+
+
+

package/docs/account/enterprise.mdx

@@ -0,0 +1,97 @@
+---
+title: "Enterprise"
+sidebarTitle: "Enterprise"
+description: "30 Tests in 30 Days Guaranteed!"
+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 **30x30 Guarantee**: try TestDriver Enterprise and we guarantee you will see 30 tests in 30 days! 
+
+Unlike other QA services that take months and cost hundreds of thousands of dollars, TestDriver gets you up and running in just 30 days.
+
+<Card
+  title="Book a Call"
+  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!
+</Card>
+
+
+---
+
+## Pricing
+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:
+- **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 GitHub Actions.
+
+For more details or to get a demo [Contract Details](#contract-details). To see other plans and pricing, check out our [Pricing](/account/pricing).
+
+
+<CardGroup cols={3}>
+  <Card title="Quickly Deploy AI QA Tests">
+    Safeguard your most important user flows with generated tests.
+  </Card>
+  <Card title="Increase your total coverage">
+    Test flows never possible before with our powerful computer-use agent.
+  </Card>
+  <Card title="Spend less time on maintenance">
+    TestDriver tests automatically repair themselves.
+  </Card>
+</CardGroup>
+
+## Promotion Details
+Here's what's included in the **30x30 Promotion**:
+
+- **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.
+- **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.
+- **GitHub Integration**: Seamlessly integrate with GitHub Actions.
+- **Enterprise Dashboards**: Gain full access to our enterprise-grade test dashboards.
+
+For more details, see [Contract Details](#contract-details).
+
+---
+
+## How Does It Work?
+
+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 our GitHub Actions.
+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.
+
+---
+
+## Onboarding Process
+
+| 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 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 GitHub Actions.|
+
+---
+
+## Contract Details
+
+- **Free Trial**: Get 30 custom tests free during a 30-day trial when subscribing to the $995/month "30x30" 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.
+- **Cancellation**: Cancel anytime during your trial, for any reason.
+- **Credits**: Unused credits do not 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.
+
+---
+
+## Ready to 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.

package/docs/account/pricing.mdx

@@ -0,0 +1,26 @@
+---
+title: "Pricing"
+sidebarTitle: "Pricing"
+description: "Explore TestDriver's pricing plans and features."
+icon: "dollar-sign"
+---
+
+## TestDriver Pricing Plans
+TestDriver offers a range of pricing plans to suit different needs, from individual developers to large enterprises. Our plans are designed to provide flexibility and scalability, ensuring you can choose the right option for your testing requirements.
+
+<CardGroup cols={3}>
+  <Card title="Free" icon="check">
+    Local agent testing. Always free.
+  </Card>
+  <Card title="Business" icon="briefcase">
+    Use local or hosted runners on demand or integrated with CI for as low as $0.05/minute.
+  </Card>
+    <Card title="Enterprise" icon="shield">
+    Need advanced features? Contact us for tailored solutions. Starting at $995/month.
+  </Card>
+</CardGroup>
+
+<Tip>Every plan starts with $100 in TestDriver credits to get you off the starting line!</Tip>
+
+## Compare Plans
+To view the latest pricing and features, please visit our [Pricing Page](https://testdriver.ai/pricing).

package/docs/account/projects.mdx

@@ -0,0 +1,27 @@
+---
+title: "TestDriver Projects"
+sidebarTitle: "Projects"
+description: "Manage your projects and workflows with TestDriver."
+icon: "folder"
+---
+
+## Dashboard Project View
+In the Project tab, select a Project to see the replays for that project.
+
+<Frame caption="Click a Project to view its replays">
+  <img src="/images/content/account/projectpage.png" />
+</Frame>
+
+From the Project view, you can see all the replays (Dashes) stored for that project. Click one to see it. These will also be linked in CI for any pull requests or branches that have been tested with TestDriver.
+
+<Frame caption="Click a Replay to view, comment or share ">
+  <img src="/images/content/account/projectreplays.png" />
+</Frame>
+
+
+## New Project
+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.
+
+<Frame caption="Click a Project to view its replays">
+  <img src="/images/content/account/newprojectsettings.png" />
+</Frame>

package/docs/account/team.mdx

@@ -0,0 +1,31 @@
+---
+title: "Team"
+sidebarTitle: "Team"
+description: "Manage your team and collaborate with TestDriver."
+icon: "users"
+---
+
+## Important Settings in one place
+In the Team tab, you can manage your team name, team members, API key, and subscription.
+
+### Let's take a look at the team settings.
+<Frame caption="Team Settings">
+  <img src="/images/content/account/teampage.png" />
+</Frame>
+
+1. **Team Name**: The name of your team. This is used to identify your team in TestDriver.
+2. **API Key**: Your API key is used to authenticate your requests to the TestDriver API. You can regenerate it if you suspect it has been compromised.
+3. **Usage & Billing**: Monitor your usage and billing information. This includes your current plan, usage limits, and billing history.
+<Tip>Note: this button is where you 'Upgrade to Pro' to start your free trial.</Tip>
+4. **Replay Visibility**: Toggle whether your replays are public or private by default. This defaults to **private**.
+5. **Don't forget to save your changes!**: After making any changes, be sure to click the **Update** button to apply them.
+
+
+### Team Members
+<Frame caption="Team Members">
+  <img src="/images/content/account/team-manage.png" />
+</Frame>
+
+1. **Email Invite**: Invite new team members by entering their email address and clicking the **Invite** button. They will receive an email invitation to join your team. You can also copy the link above this option to send to everyone at once.
+2. **Removing Team Members**: To remove a team member, click the **Remove** button next to their name. This will revoke their access to your TestDriver account.
+3. **Invite Status**: The status of the invite will be shown here. If it says **Invited**, the invite has not been accepted yet. To resend it, click here.

package/docs/action/browser.mdx

@@ -116,7 +116,7 @@ jobs:
           os: ${{ matrix.os }}
           prerun: |
             # Add prerun script here
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           FORCE_COLOR: "3"

package/docs/action/os.mdx

@@ -142,7 +142,7 @@ jobs:
           os: ${{ matrix.os }}
           prerun: |
             # Add prerun script here
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           FORCE_COLOR: "3"
@@ -155,4 +155,3 @@ jobs:
 - **Prerun Scripts**: Ensure your prerun scripts are compatible with the specified operating system.
 - **Cross-Platform Testing**: Use the matrix strategy to test across multiple OS and browser combinations for maximum coverage.
 - **Linux Default**: Linux is the default operating system for most workflows and is ideal for lightweight, fast testing.
-```

package/docs/action/output.mdx

@@ -26,7 +26,7 @@ The following example demonstrates how to use the output variables to create a c
 
 ### Workflow Example
 ```yaml
-name: TestDriver.ai
+name: TestDriver
 
 permissions:
   actions: read
@@ -45,7 +45,7 @@ jobs:
     steps:
       - uses: dashcamio/testdriver@main
         version: v4.0.0
-        key: ${{ secrets.TESTDRIVER_API_KEY }}
+        key: ${{ secrets.TD_API_KEY }}
         with:
           prompt: |
             1. /run /Users/ec2-user/actions-runner/_work/testdriver/testdriver/.testdriver/test.yml

package/docs/action/performance.mdx

@@ -19,6 +19,10 @@ Parallel testing allows you to split your test actions into multiple files and r
 - Divide your test steps into smaller, independent YAML files.
 - Use the `run` command or GitHub 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 the GitHub matrix strategy.
+</Warning>
+
 Example:
 ```yaml
 strategy:

package/docs/action/prerun.mdx

@@ -2,7 +2,7 @@
 title: "Prerun Scripts"
 sidebarTitle: "Prerun Scripts"
 description: "Learn how to customize and set up your TestDriver environment to optimize your CI/CD pipeline."
-icon: "hammer"
+icon: "terminal"
 ---
 
 ## Overview
@@ -58,6 +58,30 @@ jobs:
             }
 ```
 
+## Example: Loading a Calculator App on Linux, Mac or Windows
+```yaml
+version: 5.5.5
+session: 67f00511acbd9ccac373edf7
+steps:
+  - prompt: launch a calculator
+    commands:
+      - command: exec
+        lang: shell
+        linux: |
+          linux: |
+            jumpapp /usr/bin/galculator > /dev/null 2>&1 &
+            exit
+        mac: |
+          open "/Applications/Calculator.app"
+          wait
+        windows:
+          start /B calc.exe
+          timeout /t 5
+      - command: wait-for-text
+        text: "galculator"
+        timeout: 30000
+```
+
 ---
 
 ## Key Points
@@ -75,6 +99,38 @@ jobs:
 
 ---
 
+## A Note on the Default Prerun Script
+When setting up your TestDriver environment, a default prerun script is automatically generated. This script includes essential commands to ensure your VM is ready for testing. You can customize this script to suit your specific needs, but it's important to understand that it serves as a baseline for your test environment. It looks like this:
+
+```yaml
+version: 5.1.1
+session: 67f00511acbd9ccac373edf7
+steps:
+  - prompt: launch chrome
+    commands:
+      - command: exec
+        lang: shell
+        linux: |
+          jumpapp google-chrome --disable-fre --no-default-browser-check --no-first-run "${TD_WEBSITE}" &
+          exit
+        mac: |
+          open -na "Google Chrome" --args --disable-fre --no-default-browser-check --no-first-run --disable-features=PasswordManagerEnabled "${TD_WEBSITE}" &
+          exit
+        windows:
+          Start-Process "C:/Program Files/Google/Chrome/Application/chrome.exe" -ArgumentList "--start-maximized", "${TD_WEBSITE}"
+          exit
+      - command: wait-for-text
+        text: "Google Chrome"
+        timeout: 30000
+```
+
+Take note that it defaults to launching the Chrome browser. If you want to use a different browser, you can modify the `prompt` and `commands` sections accordingly. 
+
+<Warning>
+The `wait-For-text` command is crucial for ensuring that the browser is fully loaded before proceeding with the test steps. If you are testing a webapplication, you may want to adjust the `text` parameter to match the expected title or content of the page.
+</Warning>
+
+
 ## Notes
 - Prerun scripts are executed on the VM before the test suite begins.
 - They are essential for ensuring a consistent and reliable test environment.

package/docs/action/secrets.mdx

@@ -2,7 +2,7 @@
 title: "Managing Secrets in GitHub Actions"
 sidebarTitle: "Secrets Management"
 description: "Discover how to securely configure and optimize your TestDriver environment for seamless CI/CD workflows."
-icon: "mask"
+icon: "asterisk"
 ---
 
 ## Overview
@@ -52,7 +52,7 @@ steps:
 1. Navigate to your GitHub repository.
 2. Go to **Settings** > **Secrets and variables** > **Actions**.
 3. Click **New repository secret**.
-4. Add your secrets (e.g., `TD_USERNAME`, `TD_PASSWORD`, `TESTDRIVER_API_KEY`).
+4. Add your secrets (e.g., `TD_USERNAME`, `TD_PASSWORD`, `TD_API_KEY`).
 
 For detailed instructions, refer to the [GitHub Docs on using secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets).
 
@@ -78,7 +78,7 @@ jobs:
     steps:
       - uses: testdriverai/action@main
         with:
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
           prompt: | 
             1. /run tests/signin.yml
         env:

package/docs/action/setup.mdx

@@ -2,7 +2,7 @@
 title: "GitHub Action Setup Guide"
 sidebarTitle: "Setup Guide"
 description: "Learn how to set up and configure the TestDriver GitHub Action for automated cloud-based testing in your CI/CD workflows."
-icon: "wrench"
+icon: "square-terminal"
 ---
 
 ## Overview
@@ -25,7 +25,7 @@ To execute TestDriver actions on our virtual machines, you'll need an API key. F
 3. **Copy Your API Key**: Locate and copy your API key.
 4. **Add the API Key as a GitHub Secret**:
    - Navigate to your repository settings in GitHub.
-   - Add a new secret named `TESTDRIVER_API_KEY` and paste your API key.
+   - Add a new secret named `TD_API_KEY` and paste your API key.
 
 ---
 
@@ -33,7 +33,7 @@ To execute TestDriver actions on our virtual machines, you'll need an API key. F
 Now it's time to create your first TestDriver workflow. Add the following configuration to `.github/workflows/testdriver.yml`:
 
 ```yaml
-name: TestDriver.ai
+name: TestDriver
 
 permissions:
   actions: read
@@ -57,7 +57,7 @@ jobs:
     steps:
       - uses: dashcamio/testdriver@main
         version: "v5.0.7"
-        key: ${{ secrets.TESTDRIVER_API_KEY }}
+        key: ${{ secrets.TD_API_KEY }}
         os: linux
         with:
           prompt: |
@@ -69,7 +69,7 @@ jobs:
 
 ### Key Points:
 - **Trigger Conditions**: The `on` section defines when the workflow runs (e.g., pull requests, scheduled events, or manual triggers).
-- **API Key**: The `key` field uses the `TESTDRIVER_API_KEY` secret for authentication.
+- **API Key**: The `key` field uses the `TD_API_KEY` secret for authentication.
 - **Prompt**: The `prompt` field specifies the commands to execute. In this example, the `/run` command is used to execute a test file from the repository.
 
 ---
@@ -106,7 +106,7 @@ gh pr create --web
 ---
 
 ## Output
-For details on interpreting the output of the GitHub Action, refer to the [Action Output Documentation](../output).
+For details on interpreting the output of the GitHub Action, refer to the [Action Output Documentation](action/output).
 
 ---
 

package/docs/apps/chrome-extensions.mdx

@@ -0,0 +1,41 @@
+---
+title: Testing Chrome Extensions with TestDriver
+sidebarTitle: "Chrome Extensions"
+description: "Test Chrome extensions with TestDriver"
+icon: "puzzle-piece"
+---
+
+import TestPrereqs from '/snippets/test-prereqs.mdx'
+
+# Testing Chrome Extensions with TestDriver
+TestDriver can be used to test Chrome extensions. This guide provides an overview of how to set up and run tests for your Chrome extension using TestDriver.
+
+<TestPrereqs />
+
+## How Do I Test Chrome Extensions?
+TestDriver provides a powerful solution for testing Chrome extensions. With our platform, you can easily create and run tests to ensure your extension functions as expected across different browsers and operating systems.
+## Getting Started
+You can test a preinstalled extension or test by installing an extension. If the extension is in developemt mode, turn this on by checking the "Developer mode" checkbox in the Chrome extensions page. From there you can load the unpacked extension by selecting the folder where your extension is located. To download the files onto the VM if you are performing a test on cloud hosted runners, see the [Lifecycle](/guide/lifecycle) or [Prerun](/action/prerun) docs.
+
+## Sample Test Steps
+1. Load a the Chrome Web Store.
+2. Search for the extension you want to test.
+3. Click on the extension to open its details page.
+4. Click on the "Add to Chrome" button to install the extension.
+5. Wait for the installation to complete.
+6. Click the 'puzzle piece' icon to pin the extension to the toolbar.
+7. Click on the extension icon to open it.
+
+## TestDriver in Action
+<iframe
+  width="560"
+  height="315"
+  src="https://www.youtube.com/embed/czfq4It6-pQ"
+  title="Testing Chrome Extensions with TestDriver"
+  frameborder="0"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowfullscreen
+></iframe>
+
+## Now What?
+Once you have insstalled your extension, simply create a TestDriver test to test any functionality a user would use. 

package/docs/apps/desktop-apps.mdx

@@ -0,0 +1,87 @@
+---
+title: Using TestDriver with Desktop Apps
+sidebarTitle: "Desktop Apps"
+description: "TestDriver is designed to work with any desktop application, including Electron, Java, and .NET apps."
+icon: "desktop"
+---
+
+import TestPrereqs from '/snippets/test-prereqs.mdx'
+
+TestDriver is designed to work with any desktop application, including Electron, Java, and .NET apps. This guide provides an overview of how to use TestDriver with desktop applications, including installation, configuration, and running tests.
+
+<TestPrereqs />
+
+## Sample Test Steps
+
+## TestDriver in Action
+<iframe
+  width="560"
+  height="315"
+  src="https://www.youtube.com/embed/IwJwGxHH8cA"
+  title="Assert 2+2=4"
+  frameborder="0"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowfullscreen
+></iframe>
+
+## Supported Desktop Applications
+TestDriver supports a wide range of desktop applications, including:
+- Electron apps
+- Java apps
+- .NET apps
+- Native Windows applications
+- Native Mac applications
+- Native Linux applications
+- Any other desktop application that can be run on Windows, Mac, or Linux
+## Installation
+To use TestDriver with desktop applications, no special setup is needed. Simply run the local agent to interact with applications on your local machine, or add instructions to `prerun.yaml` to tell the runner to launch or install the application. Here is an example that performs a calculation on a calculator app:
+```yaml
+version: 5.5.5
+session: 67f00511acbd9ccac373edf7
+steps:
+  - prompt: launch a calculator
+    commands:
+      - command: exec
+        lang: shell
+        linux: |
+          linux: |
+            jumpapp /usr/bin/galculator > /dev/null 2>&1 &
+            exit
+        mac: |
+          open "/Applications/Calculator.app"
+          wait
+        windows:
+          start /B calc.exe
+          timeout /t 5
+      - command: wait-for-text
+        text: "calculator"
+        timeout: 30000
+```
+
+A `calculator_test.yaml` file might look like this:
+```yaml
+version: 5.5.5
+session: 6810141e0e064b42739922f2
+steps:
+  - prompt: /try performing the operation 2 + 2 = on the calculator that is opened
+    commands:
+      - command: focus-application
+        name: galculator
+      - command: hover-image
+        description: button with number 2 on the calculator
+        action: click
+      - command: hover-image
+        description: plus button on the calculator
+        action: click
+      - command: hover-image
+        description: button with number 2 on the calculator
+        action: click
+      - command: hover-image
+        description: equals button on the calculator
+        action: click
+```
+
+## Conclusion
+TestDriver is a powerful tool for automating tests for desktop applications. With its support for a wide range of desktop platforms and its easy-to-use interface, you can quickly set up and run tests for your applications. Whether you are testing Electron apps, Java apps, or any other desktop application, TestDriver provides the tools you need to ensure your applications work as expected.
+
+