done with getting-started section (other than vscode)

Author: chottuthejimmy

docs/getting-started/ci.mdx

@@ -9,14 +9,20 @@ This guide explains how to set up TestDriver in CI/CD pipelines, using **GitHub
 
 ## Prerequisites
 
-1. **TestDriver API Key**: Obtain your API key from TestDriver and store it as a CI/CD secret (for example, `TD_API_KEY` in GitHub Actions).
+1. **Add API key to secrets**: Obtain your API key from TestDriver and store it as a [CI/CD secret](https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets) as `TD_API_KEY`.
+Also make sure to add the `TD_WEBSITE` secret to the repository with the value of the website you are testing if its a web based application.
 2. **Test Files**: Ensure your test files are saved in the `testdriver/` directory of your repository.
 
 ## Create a CI/CD workflow
 
 This example uses GitHub Actions, but the same approach can be adapted for other CI/CD platforms:
 
 1. Create a new file in your repository: `.github/workflows/testdriver.yaml`.
+
+<Note>
+  If you have already [initialized the project](/getting-started/setup) with `npx testdriverai@latest init`, the workflow file will already be created.
+</Note>
+
 2. Add the following workflow configuration:
 
 ### Example GitHub Actions workflow
@@ -33,64 +39,23 @@ on:
     - cron: '0 13 * * *'  # Every day at 1 PM UTC (adjust if needed for timezone)
 
 permissions:
-  actions: read
   contents: read
-  statuses: write
-  pull-requests: write
+  pull-requests: read
 
 jobs:
-  gather-test-files:
-    name: Setup Test Matrix (./testdriver/*.yaml)
-    runs-on: ubuntu-latest
-    outputs:
-      test_files: ${{ steps.test_list.outputs.files }}
-    steps:
-      - name: Check out repository
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.ref }}
-      - name: Find all test files and extract filenames
-        id: test_list
-        run: |
-          FILES=$(ls ./testdriver/*.yaml)
-          FILENAMES=$(basename -a $FILES)
-          FILES_JSON=$(echo "$FILENAMES" | jq -R -s -c 'split("\n")[:-1]')
-          echo "files=$FILES_JSON" >> $GITHUB_OUTPUT
 
   test:
-    needs: gather-test-files
-    strategy:
-      matrix:
-        test: ${{ fromJson(needs.gather-test-files.outputs.test_files) }}
-      fail-fast: false
-    name: ${{ matrix.test }}
+    name: TestDriver
+    runs-on: ubuntu-latest
     steps:
-      - name: Check out repository
+      - name: Checkout repository
         uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.ref }}
-          fetch-depth: 0
-
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: "20"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: NODE_ENV=production npm ci
-
-      - name: Display filename being tested
-        run: echo "Running job for file: ${{ matrix.test }}"
 
       - name: Run TestDriver
-        run: npx testdriverai@latest run testdriver/${{ matrix.test }} --headless
+        run: npx testdriverai@latest run testdriver/testdriver.yaml --headless
         env:
           TD_API_KEY: ${{ secrets.TD_API_KEY }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          FORCE_COLOR: "3"
-          TD_WEBSITE: ${{ vars.TD_WEBSITE || 'https://your-app.com' }}
-          TD_THIS_FILE: ${{ matrix.test }}
+          TD_WEBSITE: ${{ secrets.TD_WEBSITE }}
 ```
 
 ## Trigger the workflow
@@ -102,7 +67,11 @@ jobs:
 ## View results
 
 1. Navigate to the **Actions** tab in your GitHub repository (or equivalent CI/CD dashboard).
-2. Select the workflow run to view the test results.
+2. Select the workflow run to view the test results. You will also find the link to the test recording at the end of the run, the url is of the format: `https://app.dashcam.io/replay/1234567890`
+
+<Tip>
+You can also intregate our supported [reporting platform](/exporting/junit) to get more currated results.
+</Tip>
 
 <Note>
   For other CI/CD platforms, adapt the workflow syntax to match your platform's
@@ -153,3 +122,24 @@ TestDriver provides a powerful debugging interface through its platform. This in
 
 - Share test results with your team by generating a shareable link.
 - Add comments or annotations to specific steps to facilitate discussions and debugging.
+
+---
+
+## How it works
+
+1. **Trigger**: The GitHub workflow is triggered based on the conditions defined in the `on` section.
+2. **Fetch the test files**: The test files are fetched from the repository based off the current branch.
+3. **Running the tests**: The TestDriver CLI is installed and the tests are run via the `run` command.
+4. **Authentication**: The `TD_API_KEY` environment variable authenticates your account.
+5. **Dashcam Recording**: Dashcam begins recording the test execution.
+6. **Test Execution**: The TestDriver CLI executes your commands on the cloud VM.
+8. **Test Summary**: TestDriver summarizes the test and sets the exit code based on the pass or fail state.
+9. **Cleanup**: The recording is uploaded to the TestDriver platform and the VM is destroyed, and all data is wiped.
+
+---
+
+## Additional features
+
+- **Parallel testing**: You can run multiple tests in [parallel](/features/parallel-testing#setting-up-parallel-testing-with-a-matrix-strategy). The number of parallel instances depends on the plan you are on.
+- **Environment Variables**: Pass [custom environment variables](guide/authentication#step-2%3A-pass-credentials-to-the-workflow) to configure credentials that are required for the tests.
+- **Chaining Workflows**: A common workflow involves waiting for staging to deploy and testing against the staging environment by passing in the deployed url as `TD_WEBSITE` or the staging build's installation url depending on the kind of application you are testing.

docs/getting-started/editing.mdx

@@ -5,12 +5,8 @@ description: "Edit previously generated tests."
 icon: "file-pen"
 ---
 
-import YmlWarning from "/snippets/yml-warning.mdx";
-
 Test scripts are written in YAML format, making them easy to read and modify manually if you need to.
 
-<YmlWarning />
-
 <Card title="Commands Reference" icon="link" href="/commands/assert">
   Explore the available commands and their parameters.
 </Card>
@@ -27,12 +23,12 @@ Use your preferred text editor or IDE (for example, Visual Studio Code) to open
 
 Each test file consists of:
 
-- **Version**: Specifies the TestDriver version.
+- **Version**: Specifies the TestDriver version that was used to generate the test file. This is used to lock the version of TestDriver that is used to run the test.
 - **Session**: A unique identifier for the test session.
 - **Steps**: A list of prompts and commands to execute.
 
-```yaml testfile.yaml
-version: 4.2.18
+```yaml test-file.yaml
+version: 6.0.0
 session: abc1234
 steps:
   - prompt: Open Google Chrome and navigate to Airbnb
@@ -46,7 +42,8 @@ steps:
       - command: type
         text: airbnb.com
       - command: press-keys
-        keys: [enter]
+        keys: 
+          - enter
 ```
 
 <Tip>
@@ -61,7 +58,7 @@ steps:
 You can add, edit, or remove steps as needed. Each step contains:
 
 - **Prompt**: A description of the action.
-- **Commands**: The specific actions to perform.
+- **Commands**: The specific actions to perform. It is an **optional** field, meaning, if there are no `commands` the AI considers the `prompt` and generates and executes the yaml on-the-go using the [exploratory mode](/interactive/explore)
 
 #### Example edits:
 
@@ -86,7 +83,11 @@ Ensure the YAML file is properly formatted:
 
 - Use consistent indentation (2 spaces recommended).
 - Avoid trailing spaces or tabs.
-- Validate the file using a YAML linter if needed.
+- TestDriver will validate the yaml syntax and provide suggestions to fix any errors when you run the test.
+
+<Tip>
+  It is recommended to use our [VS Code extension](/getting-started/vscode) while you are editing the yaml. It will provide you with a rich experience with auto-completion, syntax highlighting, and validation.
+</Tip>
 
 ### Test the changes
 

docs/getting-started/running.mdx

@@ -17,20 +17,24 @@ npx testdriverai@latest run path/to/test.yaml
 
 This will execute the test script located at `path/to/test.yaml`. If the test passes, the command will exit with a status code of `0`. If it fails, the command will exit with a status code of `1`.
 
+<Note>
+ The path to the test file provided should be relative to the current working directory.
+</Note>
+
 ### Interactive mode
 
 To run a test interactively:
 
 1. Launch the TestDriver CLI:
 
 ```bash
-npx testdriverai@latest
+npx testdriverai@latest edit
 ```
 
 2. At the `>` prompt, type:
 
 ```bash
-/run path/to/test.yaml
+> /run path/to/test.yaml
 ```
 
 ## Notes

docs/getting-started/setup.mdx

@@ -67,7 +67,6 @@ icon: "square-terminal"
     - creating new sandbox...
       (this can take between 10 - 240 seconds)
     - connecting...
-
     >
     ```
     You can now start writing your prompts after the `>`