testdriverai 5.6.3 → 5.6.5

package/docs/importing/gherkin.mdx

@@ -9,11 +9,11 @@ This guide explains how to convert **Gherkin scenarios** into **TestDriver promp
 
 ---
 
-## What is Gherkin?
+## What's Gherkin?
 
 Gherkin is a plain-text language used to describe test scenarios in a human-readable format. It uses keywords like `Given`, `When`, `Then`, and `And` to define steps in a test.
 
-### Example Gherkin Scenario:
+### Example Gherkin scenario:
 
 ```gherkin
 Scenario: Successful login
@@ -25,11 +25,11 @@ Scenario: Successful login
 
 ---
 
-## What Are TestDriver Prompts?
+## What are TestDriver prompts?
 
-TestDriver prompts are high-level instructions that describe what the AI should do. They are written in plain text and focus on user actions or expected outcomes.
+TestDriver prompts are high-level instructions that describe what the AI should do. They're written in plain text and focus on user actions or expected outcomes.
 
-### Example Prompts:
+### Example prompts:
 
 ```yaml
 - prompt: the user is on the login page
@@ -41,9 +41,9 @@ TestDriver prompts are high-level instructions that describe what the AI should
 
 ---
 
-## Steps to Convert Gherkin to TestDriver Prompts
+## Steps to convert Gherkin to TestDriver prompts
 
-### Step 1: Understand the Mapping
+### Step 1: Understand the mapping
 
 | **Gherkin Keyword** | **TestDriver Prompt**                     |
 |----------------------|----------------------------------------------|
@@ -54,7 +54,7 @@ TestDriver prompts are high-level instructions that describe what the AI should
 
 ---
 
-### Step 2: Extract Steps from Gherkin
+### Step 2: Extract steps from Gherkin
 
 Take each step from the Gherkin scenario and rewrite it as a plain-text prompt. Remove the `Given`, `When`, `Then`, and `And` keywords, and focus on the action or expectation.
 
@@ -69,7 +69,7 @@ Take each step from the Gherkin scenario and rewrite it as a plain-text prompt.
 
 ---
 
-### Step 3: Write the Prompts in YAML Format
+### Step 3: Write the prompts in YAML format
 
 Combine the extracted prompts into a YAML file. Each step should be written as a `prompt` entry.
 
@@ -84,28 +84,28 @@ Combine the extracted prompts into a YAML file. Each step should be written as a
 
 ---
 
-### Step 4: Save the YAML File
+### Step 4: Save the YAML file
 
-1. Save the YAML content to a file (e.g., `login_test.yml`).
-2. Ensure the file is stored in the appropriate directory for your TestDriver project (e.g., `testdriver/`).
+1. Save the YAML content to a file (for example, `login_test.yaml`).
+2. Ensure the file is stored in the appropriate directory for your TestDriver project (for example, `testdriver/`).
 
 ---
 
-### Step 5: Run the Test with TestDriver
+### Step 5: Run the test with TestDriver
 
 Use the TestDriver CLI to execute the test.
 
 #### Command:
 
 ```bash
-testdriverai run login_test.yml
+testdriverai run login_test.yaml
 ```
 
 ---
 
-## Example: Full Conversion Workflow
+## Example: Full conversion workflow
 
-### Input Gherkin Scenario:
+### Input Gherkin scenario:
 
 ```gherkin
 Scenario: Add a product to the cart
@@ -124,20 +124,20 @@ Scenario: Add a product to the cart
 - prompt: the product should appear in the cart
 ```
 
-### Run the Test:
+### Run the test:
 
 ```bash
-testdriverai run add_to_cart_test.yml
+testdriverai run add_to_cart_test.yaml
 ```
 
 ---
 
-## Best Practices
+## Best practices
 
 1. **Keep Prompts Simple**: Focus on high-level actions or outcomes. Avoid including unnecessary details.
 2. **Use Descriptive Prompts**: Ensure each prompt clearly describes the action or expectation.
 3. **Test the YAML**: Run the converted YAML file to verify that it works as expected.
-4. **Organize Files**: Store YAML files in a structured directory (e.g., `testdriver/`) for easy management.
+4. **Organize Files**: Store YAML files in a structured directory (for example, `testdriver/`) for easy management.
 
 ---
 

package/docs/importing/jira.mdx

@@ -5,13 +5,13 @@ description: "Import user stories from Jira into TestDriver test files."
 icon: "file-image"
 ---
 
-# Importing User Stories from Jira into TestDriver Test Files
+# Importing user stories from Jira into TestDriver test files
 
 This guide explains how to extract **user stories** from Jira and convert them into **TestDriver test files**. By automating this process, you can ensure that your user stories are directly translated into actionable test cases for TestDriver.
 
 ---
 
-## Workflow Overview
+## Workflow overview
 
 1. **Export User Stories from Jira**: Use the Jira API to fetch user stories.
 2. **Convert User Stories to TestDriver YAML**: Transform the user stories into YAML test files.
@@ -20,26 +20,26 @@ This guide explains how to extract **user stories** from Jira and convert them i
 
 ---
 
-## Step 1: Export User Stories from Jira
+## Step 1: Export user stories from Jira
 
 ### Prerequisites
 1. **Jira API Token**: Generate an API token from your Jira account.
-2. **Jira Base URL**: Your Jira instance URL (e.g., `https://yourcompany.atlassian.net`).
+2. **Jira Base URL**: Your Jira instance URL (for example, `https://yourcompany.atlassian.net`).
 3. **Node.js**: Ensure Node.js is installed on your system.
 
-### Script: Export User Stories from Jira
+### Script: Export user stories from Jira
 
 The following script fetches Jira tickets and extracts the **user story title** and **acceptance criteria**.
 
-#### Install Dependencies:
+#### Install dependencies:
 
 ```bash
 npm install axios yaml fs
 ```
 
-#### Node.js Script (`export-jira-user-stories.js`):
+#### Node.js script (`export-jira-user-stories.js`):
 
-```javascript
+```javascript [expandable]
 const axios = require('axios');
 const yaml = require('yaml');
 const fs = require('fs');
@@ -102,7 +102,7 @@ function createYamlFile(ticket) {
     steps,
   };
 
-  const fileName = `${ticket.id}.yml`;
+  const fileName = `${ticket.id}.yaml`;
   const filePath = path.join(OUTPUT_DIR, fileName);
 
   fs.writeFileSync(filePath, yaml.stringify(yamlContent), 'utf8');
@@ -111,17 +111,15 @@ function createYamlFile(ticket) {
 
 // Run the script
 fetchJiraTickets();
-
-
 ```
 
 ---
 
-## Step 2: Convert User Stories to TestDriver YAML
+## Step 2: Convert user stories to TestDriver YAML
 
 The script above generates a YAML file for each Jira ticket. Each file contains the **acceptance criteria** as `prompt` entries.
 
-### Example YAML File (`testdriver_tests/PROJ-123.yml`):
+### Example YAML file (`testdriver_tests/PROJ-123.yaml`):
 
 ```yaml
 version: 4.2.18
@@ -131,41 +129,42 @@ steps:
   - prompt: The login page is responsive on mobile devices.
 
 
-```---
+```
+---
 
-## Step 3: Save and Organize Test Files
+## Step 3: Save and organize test files
 
 1. The generated YAML files will be saved in the `testdriver_tests/` directory.
 2. Ensure the directory is part of your TestDriver project structure.
 
 ---
 
-## Step 4: Run Tests with TestDriver
+## Step 4: Run tests with TestDriver
 
 Use the TestDriver CLI to execute the generated test files.
 
-### Run a Single Test File:
+### Run a single test file:
 
 ```bash
-testdriverai run testdriver_tests/PROJ-123.yml
+testdriverai run testdriver_tests/PROJ-123.yaml
 
 
 ```
 
-### Run All Test Files:
+### Run all test files:
 
 ```bash
-testdriverai run testdriver_tests/*.yml
+testdriverai run testdriver_tests/*.yaml
 ```
 
 ---
 
-## Best Practices
+## Best practices
 
-1. **Field Mapping**: Ensure the correct Jira field ID (e.g., `customfield_12345`) is used for "Acceptance Criteria."
+1. **Field Mapping**: Ensure the correct Jira field ID (for example, `customfield_12345`) is used for "Acceptance Criteria."
 2. **Secure Credentials**: Store Jira API credentials in environment variables or secrets.
 3. **Review Generated Files**: Manually review the YAML files to ensure they align with your testing requirements.
-4. **Organize Tests**: Use a structured directory (e.g., `testdriver_tests/`) to manage your test files.
+4. **Organize Tests**: Use a structured directory (for example, `testdriver_tests/`) to manage your test files.
 
 ---
 

package/docs/importing/testrail.mdx

@@ -9,7 +9,7 @@ This guide explains how to extract **test cases** from TestRail and convert them
 
 ---
 
-## Workflow Overview
+## Workflow overview
 
 1. **Export Test Cases from TestRail**: Use the TestRail API to fetch test cases.
 2. **Convert Test Cases to TestDriver YAML**: Transform the test cases into YAML test files.
@@ -18,26 +18,26 @@ This guide explains how to extract **test cases** from TestRail and convert them
 
 ---
 
-## Step 1: Export Test Cases from TestRail
+## Step 1: Export test cases from TestRail
 
 ### Prerequisites
 1. **TestRail API Key**: Obtain your API key from TestRail.
-2. **TestRail Base URL**: Your TestRail instance URL (e.g., `https://yourcompany.testrail.io`).
+2. **TestRail Base URL**: Your TestRail instance URL (for example, `https://yourcompany.testrail.io`).
 3. **Node.js**: Ensure Node.js is installed on your system.
 
-### Script: Export Test Cases from TestRail
+### Script: Export test cases from TestRail
 
 The following script fetches TestRail test cases and extracts the **title** and **steps**.
 
-#### Install Dependencies:
+#### Install dependencies:
 
 ```bash
 npm install axios yaml fs
 ```
 
-#### Node.js Script (`export-testrail-test-cases.js`):
+#### Node.js script (`export-testrail-test-cases.js`):
 
-```javascript
+```javascript [expandable]
 const axios = require('axios');
 const yaml = require('yaml');
 const fs = require('fs');
@@ -100,7 +100,7 @@ function createYamlFile(testCase) {
     steps,
   };
 
-  const fileName = `test_${testCase.id}.yml`;
+  const fileName = `test_${testCase.id}.yaml`;
   const filePath = path.join(OUTPUT_DIR, fileName);
 
   fs.writeFileSync(filePath, yaml.stringify(yamlContent), 'utf8');
@@ -113,11 +113,11 @@ fetchTestRailTestCases();
 
 ---
 
-## Step 2: Convert Test Cases to TestDriver YAML
+## Step 2: Convert test cases to TestDriver YAML
 
 The script above generates a YAML file for each TestRail test case. Each file contains the **steps** as `prompt` entries.
 
-### Example YAML File (`testdriver_tests/test_123.yml`):
+### Example YAML file (`testdriver_tests/test_123.yaml`):
 
 ```yaml
 version: 4.2.18
@@ -130,31 +130,31 @@ steps:
 
 ---
 
-## Step 3: Save and Organize Test Files
+## Step 3: Save and organize test files
 
 1. The generated YAML files will be saved in the `testdriver_tests/` directory.
 2. Ensure the directory is part of your TestDriver project structure.
 
 ---
 
-## Step 4: Run Tests with TestDriver
+## Step 4: Run tests with TestDriver
 
 Use the TestDriver CLI to execute the generated test files.
 
-### Run a Single Test File:
+### Run a Single test file:
 
 ```bash
-testdriverai run testdriver_tests/test_123.yml
+testdriverai run testdriver_tests/test_123.yaml
 ```
 
 ---
 
-## Best Practices
+## Best practices
 
-1. **Field Mapping**: Ensure the correct TestRail field ID (e.g., `custom_steps`) is used for test steps.
+1. **Field Mapping**: Ensure the correct TestRail field ID (for example, `custom_steps`) is used for test steps.
 2. **Secure Credentials**: Store TestRail API credentials in environment variables or secrets.
 3. **Review Generated Files**: Manually review the YAML files to ensure they align with your testing requirements.
-4. **Organize Tests**: Use a structured directory (e.g., `testdriver_tests/`) to manage your test files.
+4. **Organize Tests**: Use a structured directory (for example, `testdriver_tests/`) to manage your test files.
 
 ---
 

package/docs/integrations/electron.mdx

@@ -9,11 +9,11 @@ To integrate **TestDriver** with a workflow that uses the **runner artifact URL*
 
 ---
 
-## Updated Workflow with TestDriver Integration
+## Updated workflow with TestDriver integration
 
 This workflow builds the application, uploads the build as an artifact, and then uses TestDriver to download the artifact via the runner artifact URL and run tests.
 
-### Workflow File: `.github/workflows/testdriver-integration.yml
+### Workflow file: `.github/workflows/testdriver-integration.yaml`
 ```yaml
 name: Build and Test with TestDriver
 
@@ -86,7 +86,7 @@ jobs:
 
 ---
 
-## Key Changes and Explanation
+## Key changes and explanation
 
 ### 1. **Artifact URL Retrieval**
 The `Get Artifact URL` step constructs the artifact URL dynamically using the GitHub repository and server URL. This ensures the TestDriver runner can download the artifact.
@@ -100,7 +100,7 @@ The `Get Artifact URL` step constructs the artifact URL dynamically using the Gi
 
 ---
 
-### 2. **Downloading the Artifact**
+### 2. **Downloading the artifact**
 The `prerun` script in the TestDriver action uses `curl` to download the artifact from the runner URL. The `GITHUB_TOKEN` is passed as a header for authentication.
 ```yaml
 prerun: |
@@ -117,7 +117,7 @@ prerun: |
 
 ---
 
-### 3. **TestDriver Integration**
+### 3. **TestDriver integration**
 The TestDriver action is configured to:
 - Download the artifact.
 - Extract the artifact.
@@ -139,7 +139,7 @@ The TestDriver action is configured to:
 
 ---
 
-## Secrets Configuration
+## Secrets configuration
 
 Add the following secrets to your GitHub repository:
 1. **`TD_API_KEY`**: Your TestDriver API key.
@@ -147,7 +147,7 @@ Add the following secrets to your GitHub repository:
 
 ---
 
-## Benefits of This Workflow
+## Benefits of this workflow
 
 1. **Dynamic Artifact Access**: Ensures TestDriver can download artifacts directly from the runner.
 2. **Automated Testing**: Integrates TestDriver to validate the application after the build.

package/docs/integrations/netlify.mdx

@@ -9,7 +9,7 @@ This guide explains how to integrate **TestDriver** with **Netlify deployments**
 
 ---
 
-## Workflow Overview
+## Workflow overview
 
 1. **Trigger Netlify Deployment**: Use Netlify's GitHub integration to deploy your application on every pull request or push to the main branch.
 2. **Run Tests on the Deployment URL**: Use the TestDriver GitHub Action to test the deployed application using the Netlify deployment URL.
@@ -20,16 +20,16 @@ This guide explains how to integrate **TestDriver** with **Netlify deployments**
 ## Prerequisites
 
 1. **Netlify GitHub Integration**: Ensure your repository is connected to Netlify for automatic deployments.
-2. **TestDriver API Key**: Store your API key as a GitHub secret (e.g., `TD_API_KEY`).
+2. **TestDriver API Key**: Store your API key as a GitHub secret (for example, `TD_API_KEY`).
 3. **Netlify Deployment URL**: Use the `DEPLOY_URL` environment variable provided by Netlify to access the deployment.
 
 ---
 
-## GitHub Actions Workflow
+## GitHub Actions workflow
 
 Here's a complete workflow to test Netlify deployments with TestDriver:
 
-### Workflow File: `.github/workflows/test-netlify.yml
+### Workflow file: `.github/workflows/test-netlify.yaml
 ```yaml
 name: Test Netlify Deployment with TestDriver
 
@@ -75,9 +75,9 @@ uses: actions/checkout@v2
 
 ---
 
-## Workflow Steps Explained
+## Workflow steps explained
 
-### 1. **Wait for Netlify Deployment**
+### 1. **Wait for Netlify deployment**
 Netlify automatically sets the `DEPLOY_URL` environment variable for each deployment. This step ensures the deployment URL is available before running tests.
 ```yaml
 - name: Wait for Netlify Deployment
@@ -94,6 +94,6 @@ Netlify automatically sets the `DEPLOY_URL` environment variable for each deploy
 
 ---
 
-### 2. **Run Tests with TestDriver**
+### 2. **Run tests with TestDriver**
 
 The TestDriver GitHub Action runs tests on the deployed application using the deployment URL. The `prompt` field specifies the test steps to execute.

package/docs/integrations/vercel.mdx

@@ -9,7 +9,7 @@ This guide explains how to integrate **TestDriver** with **Vercel deployments**
 
 ---
 
-## Workflow Overview
+## Workflow overview
 
 1. **Trigger Vercel Deployment**: Use Vercel's GitHub integration to deploy your application on every pull request or push to the main branch.
 2. **Run Tests on the Deployment URL**: Use the TestDriver GitHub Action to test the deployed application using the Vercel deployment URL.
@@ -20,16 +20,16 @@ This guide explains how to integrate **TestDriver** with **Vercel deployments**
 ## Prerequisites
 
 1. **Vercel GitHub Integration**: Ensure your repository is connected to Vercel for automatic deployments.
-2. **TestDriver API Key**: Store your API key as a GitHub secret (e.g., `TD_API_KEY`).
+2. **TestDriver API Key**: Store your API key as a GitHub secret (for example, `TD_API_KEY`).
 3. **Vercel Deployment URL**: Use the `VERCEL_URL` environment variable provided by Vercel to access the deployment.
 
 ---
 
-## GitHub Actions Workflow
+## GitHub Actions workflow
 
 Here's a complete workflow to test Vercel deployments with TestDriver:
 
-### Workflow File: `.github/workflows/test-vercel.yml`
+### Workflow file: `.github/workflows/test-vercel.yaml`
 ```yaml
 name: Test Vercel Deployment with TestDriver
 
@@ -79,9 +79,9 @@ jobs:
 
 ---
 
-## Workflow Steps Explained
+## Workflow steps explained
 
-### 1. **Wait for Vercel Deployment**
+### 1. **Wait for Vercel deployment**
 The `amondnet/vercel-action` waits for the Vercel deployment to complete and retrieves the deployment URL. This URL is stored in the `steps.vercel.outputs.url` variable.
 
 ```yaml
@@ -101,7 +101,7 @@ The `amondnet/vercel-action` waits for the Vercel deployment to complete and ret
 
 ---
 
-### 2. **Run Tests with TestDriver**
+### 2. **Run tests with TestDriver**
 The TestDriver GitHub Action runs tests on the deployed application using the deployment URL. The `prompt` field specifies the test steps to execute.
 
 ```yaml
@@ -125,7 +125,7 @@ The TestDriver GitHub Action runs tests on the deployed application using the de
 
 ---
 
-## Example TestDriver Prompt
+## Example TestDriver prompt
 
 The `prompt` field in the TestDriver action specifies the steps to test the Vercel deployment. For example:
 
@@ -142,7 +142,7 @@ prompt: |
 
 ---
 
-## Secrets Configuration
+## Secrets configuration
 
 Add the following secrets to your GitHub repository:
 1. **`TD_API_KEY`**: Your TestDriver API key.
@@ -152,7 +152,7 @@ Add the following secrets to your GitHub repository:
 
 ---
 
-## Benefits of This Workflow
+## Benefits of this workflow
 
 1. **Automated Deployment Testing**: Automatically test every Vercel deployment, including preview and production builds.
 2. **Early Issue Detection**: Catch issues in pull requests before merging.
@@ -161,13 +161,13 @@ Add the following secrets to your GitHub repository:
 
 ---
 
-## Example Output
+## Example output
 
-### GitHub Actions Dashboard:
+### GitHub Actions dashboard:
 - ✅ **Test Vercel Deployment**: All tests passed.
 - ❌ **Test Vercel Deployment**: 1 test failed. View logs for details.
 
-### TestDriver Logs:
+### TestDriver logs:
 - **Step 1**: Opened the deployment URL.
 - **Step 2**: Verified the homepage loaded correctly.
 - **Step 3**: Clicked the "Sign Up" button.

package/docs/interactive/assert.mdx

@@ -20,9 +20,9 @@ The `/assert` command ensures that a specific condition is true within your test
 - TestDriver takes a screenshot and uses it to verify that the condition described in the `expect` field is true.
 - If the condition isn't met, the test will fail and exit immediately.
 
-## Example Usage
+## Example usage
 
-### Basic Assertion
+### Basic assertion
 ```bash
 /assert No error message is displayed
 ```
@@ -32,7 +32,7 @@ This generates the following command:
   expect: There is no error message
 ```
 
-### Asynchronous Assertion
+### Asynchronous assertion
 To speed up tests, use `async: true` to allow the test to continue without waiting for the assertion to pass:
 ```yaml
 - command: assert

package/docs/interactive/dry.mdx

@@ -1,27 +1,27 @@
 ---
 title: "/dry"
 sidebarTitle: "/dry"
-description: "See and write a test plan without running the commands."
+description: "See and write a test file without running the commands."
 icon: "forward-step"
 ---
 
 ## Description
-The `/dry` command is used to create a test plan and write to a specified file. This command won't run steps it creates. It's a **dry** run. 
+The `/dry` command is used to create a test file and write to a specified file. This command won't run steps it creates. It's a **dry** run. 
 
 ## Usage
 ```bash
 /dry <file>
 ```
 
-## Example Usage
+## Example usage
 ```bash
 testdriverai <filename.yaml>
 > /dry click the 'log in' button
 ```
-This command generates the steps to `click the 'log in' button` with an explanation and adds them to the current test plan, without executing any command.
+This command generates the steps to `click the 'log in' button` with an explanation and adds them to the current test file, without executing any command.
 
 ## Behavior
-- TestDriver will create steps for the test plan, writing them in the file.
+- TestDriver will create steps for the test file, writing them in the file.
 - TestDriver will also show the reasoning and test steps in the CLI:
 
 ```bash
@@ -43,8 +43,8 @@ thinking...
 ```
 ## Protips
 - Ensure you run the `testdriverai` command with a valid file path before using `/dry`.
-- Use descriptive filenames for your test plans to make them easier to identify.
-- Combine `/dry` with `/undo` to write test plans without executing them.
+- Use descriptive filenames for your test files to make them easier to identify.
+- Combine `/dry` with `/undo` to write test files without executing them.
 
 
 ## Notes

package/docs/interactive/explore.mdx

@@ -1,13 +1,13 @@
 ---
 title: "/explore"
 sidebarTitle: "/explore"
-description: "Create and execute a test plan"
+description: "Create and execute a test file"
 icon: "play-pause"
 ---
 
 ## Description
 
-The `/explore` command is used to execute a single step in a test plan and add it to a specified file. This command generates and performs steps in an interactive way while creating a test plan.
+The `/explore` command is used to execute a single step in a test file and add it to a specified file. This command generates and performs steps in an interactive way while creating a test file.
 
 <Tip>`/explore` is the default command sent to TestDriver when no command is provided.</Tip>
 
@@ -17,11 +17,11 @@ testdriverai <filename.yaml>
 /run prompt
 ```
 
-## Example Usage
+## Example usage
 ```bash
 > /explore add an item to the shopping cart
 ```
-This command creates the command step(s) necessary to add an item to the shopping cart in the specified test plan, executing the generated command(s) after writing them into the test plan. If there are intermediate steps to be taken, they are added to the test plan as well.
+This command creates the command step(s) necessary to add an item to the shopping cart in the specified test file, executing the generated command(s) after writing them into the test file. If there are intermediate steps to be taken, they're added to the test file as well.
 
 ```bash
 thinking...
@@ -29,7 +29,7 @@ thinking...
     To add an item to the shopping cart, we need to identify
     the "Add to Cart" button from the screenshot. However,
     since the screenshot shows a code editor, we need to
-    assume the button is not visible here. Let's proceed with
+    assume the button isn't visible here. Let's proceed with
     a generic approach:
     
     commands:
@@ -74,19 +74,19 @@ thinking...
 
 
 ## Behavior
-- TestDriver will generate an idea to complete the task, try to execute it, and add the steps to the test plan.
+- TestDriver will generate an idea to complete the task, try to execute it, and add the steps to the test file.
 - The steps will be executed in the order generated.
-- If the steps are successful, they are added to the test plan file.
+- If the steps are successful, they're added to the test file.
 - If the steps fail, TestDriver will attempt to fall back to AI, undo the last step and provide an explanation of what went wrong. The AI will retry the step with new commands.
 - If the commands are successful, the program will output the results and exit with code `0`.
 - If any failures occur during the test, the program will output the errors and exit with code `1`.
 
 ## Protips
 - Use descriptive prompts for higher success with generating test steps with `/explore`.
-- Use `/explore` multiple times in succession to build a comprehensive test plan.
+- Use `/explore` multiple times in succession to build a comprehensive test file.
 
 ## Gotchas
 - The AI will retry 3 times if it can't complete the task.
 
 ## Notes
-- The `/explore` command is ideal for creating test plans in an interactive session.
+- The `/explore` command is ideal for creating test files in an interactive session.