testdriverai 5.5.5 → 5.5.6

package/docs/features/cross-platform.mdx

@@ -1,10 +1,11 @@
 ---
-title: "Cross-Platform Testing with TestDriver.ai"
+title: "Cross-Platform Testing with TestDriver"
 sidebarTitle: "Cross-Platform Testing"
-description: "Discover how TestDriver.ai enables seamless cross-platform testing across Windows, Linux, and Mac operating systems."
+description: "Discover how TestDriver enables seamless cross-platform testing across Windows, Linux, and Mac operating systems."
+icon: "computer"
 ---
 
-TestDriver.ai provides robust cross-platform support, enabling you to run tests seamlessly on **Windows**, **Linux**, and **Mac** operating systems. This flexibility ensures that your applications are tested in environments that match your users' setups.
+TestDriver provides robust cross-platform support, enabling you to run tests seamlessly on **Windows**, **Linux**, and **Mac** operating systems. This flexibility ensures that your applications are tested in environments that match your users' setups.
 
 ## Specifying the Operating System
 
@@ -24,7 +25,7 @@ jobs:
       - uses: testdriverai/action@main
         with:
           os: linux
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
           prompt: |
             1. Open the browser
             2. Navigate to example.com
@@ -54,7 +55,7 @@ jobs:
       - uses: testdriverai/action@main
         with:
           os: mac
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
           prompt: |
             1. Open the browser
             2. Navigate to example.com
@@ -75,7 +76,7 @@ jobs:
 
 ## Write Once, Run Anywhere
 
-TestDriver.ai uses **selectorless testing**, meaning tests are written in a generic format that works across all platforms. The AI dynamically adapts to the environment, ensuring that the same test can run on Windows, Linux, and Mac without modification.
+TestDriver uses **selectorless testing**, meaning tests are written in a generic format that works across all platforms. The AI dynamically adapts to the environment, ensuring that the same test can run on Windows, Linux, and Mac without modification.
 
 ### Benefits of Selectorless Testing
 
@@ -88,7 +89,7 @@ TestDriver.ai uses **selectorless testing**, meaning tests are written in a gene
 ```yaml
 version: 4.2.18
 steps:
-  - prompt: Open the browser and search for "TestDriver.ai"
+  - prompt: Open the browser and search for "TestDriver"
     commands:
       - command: focus-application
         name: Google Chrome
@@ -97,7 +98,7 @@ steps:
         description: main search bar
         action: click
       - command: type
-        text: TestDriver.ai
+        text: TestDriver
       - command: press-keys
         keys: [enter]
 

package/docs/features/generation.mdx

@@ -1,10 +1,11 @@
 ---
-title: "Test Generation with TestDriver.ai"
+title: "Test Generation with TestDriver"
 sidebarTitle: "Test Generation"
 description: "Simplify test creation with AI-driven exploratory testing."
+icon: "wand-sparkles"
 ---
 
-Writing tests can be a tedious and time-consuming task. TestDriver.ai can generate tests just by exploring your app! This guide will show you how to generate tests using TestDriver.ai.
+Writing tests can be a tedious and time-consuming task. TestDriver can generate tests just by exploring your app! This guide will show you how to generate tests using TestDriver.
 
 # Generate Exploratory Tests
 
@@ -29,7 +30,7 @@ Then, run the `generate` command.
 /generate web 10
 ```
 
-This will generate 10 tests within the `testdriver/generate` directory. You can change the number of tests generated by changing the number after `10`. The generated tests will be in the form of a `.js` file, and you can run them using your test runner of choice.
+This will generate 10 tests within the `testdriver/generate` directory. You can change the number of tests generated by changing the number after `10`. The generated tests will be in the form of a `.yaml` file, and you can run them using your test runner of choice (local or cloud hosted).
 
 ```bash
 > /generate web 5

package/docs/features/github.mdx

@@ -1,26 +1,30 @@
 ---
-title: "GitHub Integration with TestDriver.ai"
+title: "GitHub Integration with TestDriver"
 sidebarTitle: "GitHub Integration"
-description: "Explore how TestDriver.ai enhances GitHub workflows with branch creation, manual dispatch, and detailed outputs for seamless test management."
+description: "Explore how TestDriver enhances GitHub workflows with branch creation, manual dispatch, and detailed outputs for seamless test management."
+icon: "github"
 ---
+import GitignoreWarning from '/snippets/gitignore-warning.mdx';
 
-TestDriver.ai offers advanced GitHub integration features, including the ability to create its own branches, trigger workflows manually from the GitHub Actions UI, and provide detailed outputs for debugging and reporting. These features make it easier to manage test workflows, collaborate on test results, and maintain a clean and automated testing pipeline.
+TestDriver offers advanced GitHub integration features, including the ability to create its own branches, trigger workflows manually from the GitHub Actions UI, and provide detailed outputs for debugging and reporting. These features make it easier to manage test workflows, collaborate on test results, and maintain a clean and automated testing pipeline.
+
+<GitignoreWarning/>
 
 ---
 
 ## 1. **Creating Branches Automatically**
 
-TestDriver.ai can create its own branches to store test results, updates, or auto-healed tests. This ensures that test-related changes are isolated from the main codebase and can be reviewed before merging.
+TestDriver can create its own branches to store test results, updates, or auto-healed tests. This ensures that test-related changes are isolated from the main codebase and can be reviewed before merging.
 
 ### How It Works:
 
-- **Branch Creation**: TestDriver.ai creates a new branch (e.g., `test-results` or `auto-heal-updates`) during the workflow execution.
+- **Branch Creation**: TestDriver creates a new branch (e.g., `test-results` or `auto-heal-updates`) during the workflow execution.
 - **Pull Request**: A pull request is automatically opened from the new branch to the base branch (e.g., `main`), allowing developers to review the changes.
 
 ### Example Workflow with Branch Creation:
 
-```yaml
-name: TestDriver.ai Auto-Healing
+```yaml {21-24}
+name: TestDriver Auto-Healing
 
 on:
   pull_request:
@@ -34,14 +38,14 @@ jobs:
       - name: Check out repository
         uses: actions/checkout@v2
 
-      - name: Run TestDriver.ai
+      - name: Run TestDriver
         uses: testdriverai/action@main
         with:
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
           prompt: |
             1. Run all tests in the testdriver directory
           create-pr: true
-          pr-title: "TestDriver.ai Test Results"
+          pr-title: "TestDriver Test Results"
           pr-branch: test-results
           pr-test-filename: testdriver-results.yml
         env:
@@ -71,7 +75,7 @@ GitHub Actions supports manual triggering of workflows using the **workflow_disp
 ### Example Workflow with Manual Dispatch:
 
 ```yaml
-name: TestDriver.ai Manual Dispatch
+name: TestDriver Manual Dispatch
 
 on:
   workflow_dispatch:
@@ -84,10 +88,10 @@ jobs:
       - name: Check out repository
         uses: actions/checkout@v2
 
-      - name: Run TestDriver.ai
+      - name: Run TestDriver
         uses: testdriverai/action@main
         with:
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
           prompt: |
             1. Run all tests in the testdriver directory
         env:
@@ -108,11 +112,11 @@ Run Steps
 
 ## 3. **GitHub Actions Output**
 
-TestDriver.ai provides detailed outputs during workflow execution, which are visible in the **Actions** tab of your repository. These outputs include:
+TestDriver provides detailed outputs during workflow execution, which are visible in the **Actions** tab of your repository. These outputs include:
 - **Test Summary**: A high-level overview of the test results.
 - **Logs**: Step-by-step logs of the test execution.
 - **Screenshots and GIFs**: Visual feedback for debugging.
-- **Links to Dashcam.io**: Direct links to detailed test recordings and results.
+- **Links to TestDriver Dashcam.io Replays**: Direct links to detailed test recordings and results.
 
 ### Example Outputs:
 
@@ -120,7 +124,7 @@ TestDriver.ai provides detailed outputs during workflow execution, which are vis
 - ✅ All tests passed.
 - ❌ 2 tests failed.
 
-#### **TestDriver.ai Replay**:
+#### **TestDriver Replay**:
 
 ```markdown
 [View Full Test Results](https://app.testdriver.ai/...)
@@ -129,7 +133,7 @@ TestDriver.ai provides detailed outputs during workflow execution, which are vis
 ---
 
 ### Using Outputs in Workflows:
-You can capture and use TestDriver.ai outputs in subsequent steps of your workflow. For example, you can post the test summary as a comment on a pull request.
+You can capture and use TestDriver outputs in subsequent steps of your workflow. For example, you can post the test summary as a comment on a pull request.
 
 #### Example:
 
@@ -158,4 +162,4 @@ You can capture and use TestDriver.ai outputs in subsequent steps of your workfl
 2. **Manual Dispatch**: Trigger workflows on demand from the GitHub Actions UI.
 3. **Detailed Outputs**: Access logs, summaries, and visual feedback directly in the Actions tab.
 
-These features make TestDriver.ai a powerful tool for managing automated testing workflows in GitHub, enabling better collaboration, debugging, and test management.
+These features make TestDriver a powerful tool for managing automated testing workflows in GitHub, enabling better collaboration, debugging, and test management.

package/docs/features/parallel-testing.mdx

@@ -1,7 +1,8 @@
 ---
-title: "Parallel Testing with TestDriver.ai"
+title: "Parallel Testing with TestDriver"
 sidebarTitle: "Parallel Testing"
-description: "Learn how to leverage GitHub Actions' matrix strategy to run TestDriver.ai tests in parallel, reducing execution time and improving scalability."
+description: "Learn how to leverage GitHub Actions' matrix strategy to run TestDriver tests in parallel, reducing execution time and improving scalability."
+icon: "server"
 ---
 
 Parallel testing allows you to run multiple tests simultaneously, significantly reducing the time required to execute your test suite. By leveraging GitHub Actions' **matrix strategy**, you can dynamically distribute your tests across multiple jobs, ensuring efficient and scalable test execution.
@@ -19,18 +20,19 @@ Parallel testing allows you to run multiple tests simultaneously, significantly
 
 ## Setting Up Parallel Testing with Matrix Strategy
 
-### Step 1: Organize Your Test Files
+<Steps>
+<Step titel="Organize Your Test Files">
 
 Ensure your test files are stored in a directory (e.g., `testdriver/`) and follow a consistent naming convention (e.g., `test1.yml`, `test2.yml`, etc.).
 
----
+</Step>
 
-### Step 2: Define the GitHub Action Workflow
+<Step title="Define the GitHub Action Workflow">
 
-Here’s an example of a GitHub Action workflow that uses the matrix strategy to run tests in parallel:
+Here's an example of a GitHub Action workflow that uses the matrix strategy to run tests in parallel:
 
 ```yaml
-name: Parallel Testing with TestDriver.ai
+name: Parallel Testing with TestDriver
 
 on:
   push:
@@ -68,10 +70,10 @@ jobs:
       - name: Check out repository
         uses: actions/checkout@v2
 
-      - name: Run TestDriver.ai
+      - name: Run TestDriver
         uses: testdriverai/action@main
         with:
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
           prompt: |
             1. /run ${{ matrix.test_file }}
         env:
@@ -79,6 +81,8 @@ jobs:
           FORCE_COLOR: "3"
 ```
 
+</Step>
+</Steps>
 ---
 
 ### Explanation of the Workflow
@@ -89,7 +93,7 @@ jobs:
 
 2. **`run-tests` Job**:
   - Uses the matrix strategy to dynamically create a job for each test file.
-  - Runs each test file in parallel using TestDriver.ai.
+  - Runs each test file in parallel using TestDriver.
 
 3. **Matrix Strategy**:
   - The `matrix.test_file` variable represents each test file.
@@ -127,4 +131,4 @@ When this workflow runs:
 
 ## Conclusion
 
-Parallel testing with the GitHub Action matrix strategy is a powerful way to speed up your TestDriver.ai test suite. By dynamically distributing tests across multiple jobs, you can ensure efficient execution and scalability, making it easier to maintain high-quality software.
+Parallel testing with the GitHub Action matrix strategy is a powerful way to speed up your TestDriver test suite. By dynamically distributing tests across multiple jobs, you can ensure efficient execution and scalability, making it easier to maintain high-quality software.

package/docs/features/reusable-snippets.mdx

@@ -1,9 +1,12 @@
 ---
-title: "Reusable Snippets in TestDriver.ai"
+title: "Reusable Snippets in TestDriver"
 sidebarTitle: "Reusable Snippets"
-description: "Discover how to modularize your test workflows using reusable YAML snippets in TestDriver.ai for improved maintainability and scalability."
+description: "Discover how to modularize your test workflows using reusable YAML snippets in TestDriver for improved maintainability and scalability."
+icon: "repeat"
 ---
 
+import GitignoreWarning from '/snippets/gitignore-warning.mdx'
+
 Reusable snippets in TestDriver allow you to modularize your test steps by creating smaller, reusable YAML files that can be embedded into larger test workflows. This approach improves test maintainability, reduces duplication, and makes your test suite more organized and scalable.
 
 ---
@@ -24,8 +27,8 @@ Reusable snippets are YAML files containing a set of test steps that perform a s
 ---
 
 ## How to Create and Use Reusable Snippets
-
-### Step 1: Create a Snippet
+<Steps>
+<Step title="Create a Snippet">
 
 Save a YAML file containing the reusable steps. For example, create a `snippets/login.yaml` file for logging into an application:
 
@@ -51,10 +54,9 @@ steps:
         description: log in button
         action: click
 ```
+</Step>
 
----
-
-### Step 2: Reference the Snippet in a Test
+<Step title="Reference the Snippet in a Test">
 
 Use the `run` command to include the snippet in your main test file. For example:
 
@@ -70,10 +72,9 @@ steps:
         description: dashboard link in the navigation bar
         action: click
 ```
+</Step>
 
----
-
-### Step 3: Parameterize Inputs
+<Step title="Parameterize Inputs">
 
 Use environment variables to pass dynamic data like usernames and passwords. Define these variables in your `.env` file or CI/CD pipeline:
 
@@ -81,7 +82,11 @@ Use environment variables to pass dynamic data like usernames and passwords. Def
 TD_USERNAME=your_username
 TD_PASSWORD=your_password
 ```
----
+
+<GitignoreWarning/>
+</Step>
+</Steps>
+
 
 ## Example: Combining Multiple Snippets
 
@@ -99,8 +104,7 @@ steps:
       - command: run
         file: snippets/add_to_cart.yaml
 ```
-
----
+--- 
 
 ## Best Practices for Reusable Snippets
 
@@ -121,4 +125,4 @@ steps:
 
 ---
 
-Reusable snippets are a cornerstone of efficient test design in TestDriver.ai. By modularizing your tests, you can create a scalable, maintainable, and reusable test suite that adapts to your application's evolving needs. Start by creating snippets for common actions like login or navigation, and expand your library as your test suite grows.
+Reusable snippets are a cornerstone of efficient test design in TestDriver. By modularizing your tests, you can create a scalable, maintainable, and reusable test suite that adapts to your application's evolving needs. Start by creating snippets for common actions like login or navigation, and expand your library as your test suite grows.

package/docs/features/selectorless.mdx

@@ -1,10 +1,13 @@
 ---
-title: "Selectorless Testing with TestDriver.ai"
+title: "Selectorless Testing with TestDriver"
 sidebarTitle: "Selectorless Testing"
 description: "Selectorless testing approach simplifies end-to-end testing by using natural language and AI vision."
+icon: "eye"
 ---
 
-Selectorless testing eliminates the need for brittle selectors like CSS classes, IDs, or XPath. Instead, TestDriver uses natural language prompts and AI-powered vision to interact with applications as a user would. This makes tests more resilient to UI changes and reduces maintenance overhead.
+Selectorless testing eliminates the need for brittle selectors like CSS classes, IDs, or XPath. 
+
+Instead, TestDriver uses natural language prompts and AI-powered vision to interact with applications as a user would. This makes tests more resilient to UI changes and reduces maintenance overhead.
 
 - Selectorless testing focuses on **what the user sees** rather than **how the UI is implemented**.
 - Tests are resilient to changes like text updates, class renaming, or minor layout adjustments.
@@ -59,4 +62,6 @@ For example:
 const button = await page.$('button[class="sign-up-btn"]');
 ```
 
-If the class name changes, the test will break, requiring updates to the test code. Selectorless testing avoids this by focusing on the intent of the interaction rather than the implementation details.
+<Warning>When using legacy frameworks, if the class name changes, the test will break, requiring updates to the test code!</Warning> 
+
+<Check>Selectorless testing avoids this by focusing on the intent of the interaction rather than the implementation details.</Check>

package/docs/features/visual-assertions.mdx

@@ -1,18 +1,17 @@
 ---
-title: "Visual Assertions with TestDriver.ai"
+title: "Visual Assertions with TestDriver"
 sidebarTitle: "Visual Assertions"
-description: "Discover how TestDriver.ai leverages AI-powered visual assertions to validate UI behavior and enhance end-to-end testing."
+description: "Discover how TestDriver leverages AI-powered visual assertions to validate UI behavior and enhance end-to-end testing."
+icon: "binoculars"
 ---
 
-Visual assertions in TestDriver.ai allow you to validate that your application behaves as expected by analyzing what is displayed on the screen. This approach ensures that your tests mimic real user interactions and verify outcomes visually, making it ideal for testing UI-heavy applications and dynamic content.
+Visual assertions in TestDriver allow you to validate that your application behaves as expected by analyzing what's displayed on the screen. This approach ensures that your tests mimic real user interactions and verify outcomes visually, making it ideal for testing UI-heavy applications and dynamic content.
 
-## What Are Visual Assertions?
+## What Can TestDriver Test with Visual Assertions?
 
-Visual assertions check the state of the screen to confirm that specific elements, content, or behaviors are present. Instead of relying on selectors or static code analysis, TestDriver uses AI-powered vision to interpret the screen, ensuring robust and adaptive testing.
-
----
-
-## What Can TestDriver.ai Test with Visual Assertions?
+<Info>
+    See many of the following examples in the [TestDriver Scenarios](/scenarios/ai-chatbot)
+</Info>
 
 ### AI Chatbots
   - Validate that chatbot responses are displayed correctly.
@@ -120,4 +119,4 @@ Visual assertions check the state of the screen to confirm that specific element
 
 ---
 
-Visual assertions in TestDriver.ai empower you to test a wide range of applications and scenarios with confidence, ensuring your software delivers a seamless user experience.
+Visual assertions in TestDriver empower you to test a wide range of applications and scenarios with confidence, ensuring your software delivers a seamless user experience.

package/docs/getting-started/ci.mdx

@@ -1,15 +1,15 @@
 ---
 title: "Running in GitHub Actions"
 sidebarTitle: "Running in CI"
-description: "Learn how to set up and run tests with TestDriver.ai using GitHub Actions for seamless end-to-end testing."
+description: "Learn how to set up and run tests with TestDriver using GitHub Actions for seamless end-to-end testing."
 icon: "code-pull-request"
 ---
 
-This guide explains how to set up a basic GitHub Actions workflow to run tests using **TestDriver.ai**.
+This guide explains how to set up a basic GitHub Actions workflow to run tests using **TestDriver**.
 
 ## Prerequisites
 
-1. **TestDriver.ai API Key**: Obtain your API key from TestDriver.ai and store it as a GitHub secret (e.g., `TESTDRIVER_API_KEY`).
+1. **TestDriver API Key**: Obtain your API key from TestDriver and store it as a GitHub secret (e.g., `TD_API_KEY`).
 2. **Test Files**: Ensure your test files are saved in the `testdriver/` directory of your repository.
 
 ## Create a GitHub Actions Workflow
@@ -20,7 +20,7 @@ This guide explains how to set up a basic GitHub Actions workflow to run tests u
 ### Example Workflow: `.github/workflows/testdriver.yml`
 
 ```yaml
-name: TestDriver.ai / Run / Regressions
+name: TestDriver / Run / Regressions
 
 on:
   push:
@@ -75,7 +75,7 @@ jobs:
 
       - uses: testdriverai/action@main
         with:
-          key: ${{ secrets.TESTDRIVER_API_KEY }}
+          key: ${{ secrets.TD_API_KEY }}
           os: ${{ matrix.os }}
           version: "5.2.3"
           prompt: 1. /run testdriver/${{ matrix.test }}
@@ -101,8 +101,7 @@ jobs:
 2. Select the workflow run to view the test results.
 
 # Debugging Tests
-
-TestDriver.ai provides a powerful debugging interface through its **app.testdriver.ai** platform (formerly Dashcam). This interface allows you to analyze test runs, identify failures, and optimize your test suite with detailed visual and textual feedback.
+TestDriver provides a powerful debugging interface through its **app.TestDriver** platform (formerly Dashcam). This interface allows you to analyze test runs, identify failures, and optimize your test suite with detailed visual and textual feedback.
 
 ### Step-by-Step Execution Logs
 - View each step of the test execution, including:
@@ -117,7 +116,7 @@ TestDriver.ai provides a powerful debugging interface through its **app.testdriv
 - **Highlighting**: Elements interacted with during the test are highlighted in screenshots, helping you verify that the correct elements were targeted.
 
 ### 3. Error Details
-- For failed steps, app.testdriver.ai provides:
+- For failed steps, app.TestDriver provides:
   - **Error messages**: Detailed descriptions of what went wrong (e.g., "Element not found").
   - **Stack traces**: For advanced debugging of backend or script-related issues.
   - **Suggestions**: Recommendations for fixing common issues, such as adjusting prompts or improving element descriptions.

package/docs/getting-started/editing.mdx

@@ -45,6 +45,8 @@ steps:
         keys: [enter]
 ```
 
+<Tip>The `version` captured when you generate a test file is the version of TestDriver you used, and is not used when running the test. This does not affect your ability to use newer versions of TestDriver on existing test files nor do these need to be updated when migrating to a new version.</Tip>
+
 ### Modify the Test Steps
 You can add, edit, or remove steps as needed. Each step contains:
 

package/docs/getting-started/generating.mdx

@@ -5,7 +5,7 @@ description: "Generate test plans and integrate them into your testing workflow.
 icon: "steering-wheel"
 ---
 
-Writing tests can be a tedious and time-consuming task. TestDriver.ai can generate tests just by exploring your app! This guide will show you how to generate tests using TestDriver.ai.
+Writing tests can be a tedious and time-consuming task. TestDriver can generate tests just by exploring your app! This guide will show you how to generate tests using TestDriver.
 
 # Launch TestDriver in Interactive Mode
 

package/docs/getting-started/running.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Running Tests with TestDriver.ai"
+title: "Running Tests with TestDriver"
 sidebarTitle: "Running Tests"
 description: "Execute regression test plans for debugging and validation."
 icon: "play"
@@ -32,7 +32,7 @@ To run a test interactively:
 
 ## Notes
 
-- Ensure the YAML file is valid and follows the TestDriver.ai specification.
+- Ensure the YAML file is valid and follows the TestDriver specification.
 - The default file path is `testdriver/testdriver.yaml` if no file is specified.
 
 <Card

package/docs/getting-started/setup.mdx

@@ -1,18 +1,11 @@
 ---
-title: "Advanced Setup"
-sidebarTitle: "Advanced Setup"
-description: "Comprehensive guide to installing and setting up TestDriver.ai for your testing needs."
+title: "Setting up TestDriver CLI"
+sidebarTitle: "CLI Setup"
+description: "Follow these steps to install and set up TestDriver CLI."
 icon: "square-terminal"
 ---
 
 
-### **TestDriver.ai Installation Guide**
-
-Follow these steps to install and set up TestDriver.ai:
-
----
-
-
 <Steps>
 
   <Step title="Install NodeJS">
@@ -40,7 +33,7 @@ Follow these steps to install and set up TestDriver.ai:
     Install the TestDriver CLI globally using npm:
   
     ```bash
-    npm install -g testdriverai
+    npm install -g testdriverai@beta
     ```
   
     Verify the installation:
@@ -53,7 +46,7 @@ Follow these steps to install and set up TestDriver.ai:
 
   <Step title="Set Up Your Test Runner">
 
-    TestDriver.ai requires a runner to execute tests. You can use either a hosted sandbox or your own computer.
+    TestDriver requires a runner to execute tests. You can use either a hosted sandbox or your own computer.
     
     - **TestDriver Sandbox** - Run tests in a ephemeral linux virtual machine. Recommended for ease of use, added privacy, and parallelization. Requires a TestDriver API key.
     - **Local Runner** - Run tests on your own computer. Recommended for working with existing user sessions, files, and applications. Requires additional setup.