testdriverai 5.6.2 → 5.6.4

package/agent.js

@@ -233,14 +233,14 @@ const haveAIResolveError = async (
 
   let safeKey = JSON.stringify(eMessage);
   errorCounts[safeKey] = errorCounts[safeKey] ? errorCounts[safeKey] + 1 : 1;
+  
+  logger.error(chalk.red("Error detected"));
 
-  logger.error(eMessage);
+  log.prettyMarkdown(eMessage);
 
   logger.debug("%j", error);
   logger.debug("%s", error.stack);
 
-  log.prettyMarkdown(eMessage);
-
   // if we get the same error 3 times in `run` mode, we exit
   if (errorCounts[safeKey] > errorLimit - 1) {
     logger.info(chalk.red("Error loop detected. Exiting."));
@@ -1097,7 +1097,7 @@ let run = async (file = thisFile, shouldSave = false, shouldExit = true) => {
       return await exit(true);
     } else if (!step.commands) {
       logger.info(chalk.yellow("No commands found, running exploratory"));
-      await exploratoryLoop(step.prompt, false, true);
+      return await exploratoryLoop(step.prompt, false, true);
     }
 
     if (shouldSave) {

package/docs/account/dashboard.mdx

@@ -4,13 +4,10 @@ sidebarTitle: "Dashboard"
 description: "Explore your TestDriver dashboard and its features."
 icon: "gauge"
 ---
-## Welcome to your TestDriver Dashboard
+## 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
+## 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.
-
-
-
+- **Usage & Billing**: Monitor your usage and credits in real-time.

package/docs/account/enterprise.mdx

@@ -1,12 +1,12 @@
 ---
 title: "Enterprise"
 sidebarTitle: "Enterprise"
-description: "30 Tests in 30 Days Guaranteed!"
+description: "The TestDriver 4x4 Guarantee!"
 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! 
+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! 
 
 Unlike other QA services that take months and cost hundreds of thousands of dollars, TestDriver gets you up and running in just 30 days.
 
@@ -35,30 +35,31 @@ For more details or to get a demo [Contract Details](#contract-details). To see
   <Card title="Quickly Deploy AI QA Tests">
     Safeguard your most important user flows with generated tests.
   </Card>
-  <Card title="Increase your total coverage">
+  <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">
+  <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**:
+## Promotion details
+Here's what's included in all Enterprise plans:
 
 - **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.
-- **GitHub Integration**: Seamlessly integrate with GitHub Actions.
+- **CI/CD Integration**: Seamlessly integrate with your CI/CD pipeline.
 - **Enterprise Dashboards**: Gain full access to our enterprise-grade test dashboards.
 
 For more details, see [Contract Details](#contract-details).
 
 ---
 
-## How Does It Work?
+## 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.
@@ -68,30 +69,30 @@ For more details, see [Contract Details](#contract-details).
 
 ---
 
-## Onboarding Process
+## 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.   |
+| **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 GitHub Actions.|
 
 ---
 
-## Contract Details
+## Contract details
 
-- **Free Trial**: Get 30 custom tests free during a 30-day trial when subscribing to the $995/month "30x30" plan.
+- **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.
+- **Renewal**: The contract renews annually. You can pay monthly or 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.
+- **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.
 
 ---
 
-## Ready to Get Started?
+## 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

@@ -5,14 +5,14 @@ description: "Explore TestDriver's pricing plans and features."
 icon: "dollar-sign"
 ---
 
-## TestDriver Pricing Plans
+## 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">
+  <Card title="Hobby" icon="check">
     Local agent testing. Always free.
   </Card>
-  <Card title="Business" icon="briefcase">
+  <Card title="Pro" 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">
@@ -22,5 +22,5 @@ TestDriver offers a range of pricing plans to suit different needs, from individ
 
 <Tip>Every plan starts with $100 in TestDriver credits to get you off the starting line!</Tip>
 
-## Compare Plans
+## Compare plans
 To view the latest pricing and features, please visit our [Pricing Page](https://testdriver.ai/pricing).

package/docs/account/projects.mdx

@@ -5,7 +5,7 @@ description: "Manage your projects and workflows with TestDriver."
 icon: "folder"
 ---
 
-## Dashboard Project View
+## 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">
@@ -19,7 +19,7 @@ From the Project view, you can see all the replays (Dashes) stored for that proj
 </Frame>
 
 
-## New Project
+## 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">

package/docs/account/team.mdx

@@ -5,7 +5,7 @@ description: "Manage your team and collaborate with TestDriver."
 icon: "users"
 ---
 
-## Important Settings in one place
+## 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.
@@ -21,11 +21,11 @@ In the Team tab, you can manage your team name, team members, API key, and subsc
 5. **Don't forget to save your changes!**: After making any changes, be sure to click the **Update** button to apply them.
 
 
-### Team Members
+### 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.
+3. **Invite Status**: The status of the invite will be shown here. If it says **Invited**, the invite hasn't been accepted yet. To resend it, click here.

package/docs/action/browser.mdx

@@ -15,18 +15,18 @@ By using prerun scripts, you can:
 
 ---
 
-## Supported Browsers
+## Supported browsers
 The following browsers can be installed and launched using prerun scripts:
 - **Google Chrome**
 - **Mozilla Firefox**
 
 ---
 
-## Prerun Script Example: Installing and Launching Browsers
+## Prerun script example: Installing and launching browsers
 The following example demonstrates how to install and launch Google Chrome or Firefox on Windows, macOS, and Linux using a prerun script.
 
-### Example: Prerun Script
-```yaml
+### Example: `prerun` script
+```yaml [expandable]
 prerun: |
   if [ "${{ matrix.browser }}" == "chrome" ]; then
     if [ "${{ matrix.os }}" == "windows" ]; then
@@ -67,10 +67,10 @@ prerun: |
 
 ---
 
-## Testing Multiple Browsers
+## Testing multiple browsers
 You can use the GitHub matrix strategy to test your application across multiple browsers. This ensures comprehensive browser compatibility testing.
 
-### Example: Matrix Strategy for Browser Testing
+### Example: Matrix strategy for browser testing
 ```yaml
 strategy:
   matrix:
@@ -78,8 +78,8 @@ strategy:
     browser: [chrome, firefox]
 ```
 
-### Full Workflow Example
-```yaml
+### Full workflow example
+```yaml [expandable]
 name: Test Action
 
 permissions:
@@ -127,4 +127,4 @@ jobs:
 ## Notes
 - **Cross-Platform Compatibility**: Ensure your prerun scripts are compatible with the operating system specified in the matrix.
 - **Browser Versions**: Always install the latest stable versions of browsers to ensure compatibility with modern web standards.
-- **Performance**: Launching browsers in prerun scripts ensures they are ready for immediate use during tests, reducing setup time.
+- **Performance**: Launching browsers in prerun scripts ensures they're ready for immediate use during tests, reducing setup time.

package/docs/action/os.mdx

@@ -10,7 +10,7 @@ The TestDriver GitHub Action allows you to run tests on multiple operating syste
 
 ---
 
-## Supported Operating Systems
+## Supported operating systems
 The following operating systems are currently supported:
 
 | OS       | Version                  | Instance Type | Architecture   | Notes                          |
@@ -21,22 +21,22 @@ The following operating systems are currently supported:
 
 ---
 
-## Configuring the Operating System
+## Configuring the operating system
 To specify the operating system, use the `os` parameter in the GitHub Action configuration. For example:
 
-### Example: Running a Test on Windows
+### Example: Running a test on Windows
 ```yaml
 with:
   os: windows
 ```
 
-### Example: Running a Test on macOS
+### Example: Running a test on macOS
 ```yaml
 with:
   os: mac
 ```
 
-### Example: Running a Test on Linux
+### Example: Running a test on Linux
 ```yaml
 with:
   os: linux
@@ -44,16 +44,16 @@ with:
 
 ---
 
-## Prerun Scripts and OS-Specific Commands
+## Prerun scripts and OS-specific commands
 Prerun scripts are executed on the specified operating system. The scripting language depends on the OS:
 - **Windows**: Use PowerShell.
 - **macOS**: Use Bash.
 - **Linux**: Use Bash.
 
-### Example: Installing Browsers Based on OS
+### Example: Installing browsers based on OS
 The following example demonstrates how to install Google Chrome or Firefox on Windows, macOS, and Linux using a prerun script:
 
-```yaml
+```yaml [expandable]
 prerun: |
   if [ "${{ matrix.browser }}" == "chrome" ]; then
     if [ "${{ matrix.os }}" == "windows" ]; then
@@ -88,10 +88,10 @@ prerun: |
 
 ---
 
-## Testing Multiple Operating Systems and Browsers
+## Testing multiple operating systems and browsers
 You can use the GitHub matrix strategy to test your application across multiple operating systems and browsers. This ensures comprehensive coverage for your tests.
 
-### Example: Matrix Strategy for OS and Browser Testing
+### Example: Matrix strategy for OS and browser testing
 ```yaml
 strategy:
   matrix:
@@ -99,8 +99,8 @@ strategy:
     browser: [chrome, firefox]
 ```
 
-### Full Workflow Example
-```yaml
+### Full workflow example
+```yaml [expandable]
 name: Test Action
 
 permissions:

package/docs/action/output.mdx

@@ -10,7 +10,7 @@ The TestDriver GitHub Action provides several output variables that can be used
 
 ---
 
-## Output Variables
+## Output variables
 
 | Variable   | Description                                                                 |
 |------------|-----------------------------------------------------------------------------|
@@ -21,11 +21,11 @@ The TestDriver GitHub Action provides several output variables that can be used
 
 ---
 
-## Example: Creating a Comment on a Pull Request
+## Example: Creating a comment on a pull request
 The following example demonstrates how to use the output variables to create a comment on a pull request after every TestDriver execution.
 
-### Workflow Example
-```yaml
+### Workflow example
+```yaml [expandable]
 name: TestDriver
 
 permissions:
@@ -48,7 +48,7 @@ jobs:
         key: ${{ secrets.TD_API_KEY }}
         with:
           prompt: |
-            1. /run /Users/ec2-user/actions-runner/_work/testdriver/testdriver/.testdriver/test.yml
+            1. /run /Users/ec2-user/actions-runner/_work/testdriver/testdriver/.testdriver/test.yaml
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           FORCE_COLOR: "3"
@@ -71,13 +71,13 @@ jobs:
 
 ---
 
-## Use Cases for Output Variables
+## Use cases for output variables
 
-### 1. Post Test Results as Comments
+### 1. Post test results as comments
 Use the `summary` and `markdown` outputs to post detailed test results as comments on pull requests. This provides immediate feedback to developers.
 
-### 2. Send Notifications on Failure
-Use the `success` output to trigger notifications (e.g., email or Slack) when a test fails.
+### 2. Send notifications on failure
+Use the `success` output to trigger notifications (for example, email or Slack) when a test fails.
 
 Example:
 ```yaml
@@ -88,7 +88,7 @@ Example:
     # Add your notification logic here
 ```
 
-### 3. Integrate with Third-Party Tools
+### 3. Integrate with third-party tools
 Use the `link` output to upload test results to third-party test reporting tools or dashboards.
 
 ---

package/docs/action/performance.mdx

@@ -10,12 +10,12 @@ Optimizing your TestDriver tests can significantly reduce execution time, ensuri
 
 ---
 
-## Tips for Improving Performance
+## Tips for improving performance
 
-### 1. Use Parallel Testing
+### 1. Use parallel testing
 Parallel testing allows you to split your test actions into multiple files and run them simultaneously. This can drastically reduce the total runtime of your test suite.
 
-#### How to Implement Parallel Testing
+#### How to implement parallel testing
 - Divide your test steps into smaller, independent YAML files.
 - Use the `run` command or GitHub matrix strategy to execute these files in parallel.
 
@@ -28,17 +28,17 @@ Example:
 strategy:
   matrix:
     test_file: 
-      - tests/login.yml
-      - tests/search.yml
-      - tests/cart.yml
+      - tests/login.yaml
+      - tests/search.yaml
+      - tests/cart.yaml
 ```
 
 ---
 
-### 2. Use Optimized Matching Methods
+### 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.
 
-#### Example:
+#### Example
 ```yaml
 command: hover-text
 text: Sign In
@@ -49,10 +49,10 @@ method: turbo
 
 ---
 
-### 3. Use `async` Asserts
+### 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.
 
-#### Example:
+#### Example
 ```yaml
 command: assert
 expect: The user is logged in
@@ -61,7 +61,7 @@ async: true
 
 ---
 
-## Best Practices
+## Best practices
 - **Minimize AI Matching**: Use AI-powered matching methods only when necessary. For common actions, rely on optimized methods like `turbo`.
 - **Break Down Tests**: Split large, monolithic test files into smaller, focused tests to enable parallel execution.
 - **Leverage Asynchronous Features**: Use `async` properties wherever possible to avoid blocking test execution.