testdriverai 7.5.25 → 7.6.0-canary.0

package/CHANGELOG.md

@@ -1,3 +1,89 @@
+## 7.6.0-canary.0 (2026-03-13)
+
+## 🔧 Maintenance
+
+- Improve workflow reliability for package promotion between test, canary, and stable channels (358bb702)
+
+## 7.6.0-test.7 (2026-03-13)
+
+## 🔧 Maintenance
+
+- Eliminate CI race conditions in promotion pipeline and streamline release workflows [CI] (9d83f886)
+- Improve VNC URL display in CI environments [API] (9d83f886)
+- Add dynamic channel resolution system for SDK configuration [SDK] (9d83f886)
+- Update MCP server dependencies and enhance error handling [SDK] (9d83f886)
+
+## 7.6.0-test.6 (2026-03-13)
+
+## 🔧 Maintenance
+
+- Improve CI/CD pipeline reliability by eliminating race conditions in release promotion workflows [c21f708d]
+- Fix VNC URL display in continuous integration environment [API] [c21f708d]
+
+## 7.6.0-test.5 (2026-03-12)
+
+## 🔧 Maintenance
+
+- Update SDK channel configuration [SDK] (274fff79)
+
+## 7.6.0-test.4 (2026-03-12)
+
+## 🔧 Maintenance
+
+- Improve release workflow and deployment configuration [SDK] (eeea7649)
+- Add enhanced web analytics tracking for better user insights [SDK] (eeea7649)
+
+## 7.6.0-test.3 (2026-03-12)
+
+## 🔧 Maintenance
+
+- Improve release workflow automation and package promotion process [bb6be95]
+
+## 7.6.0-test.2 (2026-03-12)
+
+## 🔧 Maintenance
+
+- Add automated publishing workflows for stable and canary releases [SDK] (2972b3be)
+- Update CI workflows to improve testing efficiency and reliability [SDK] (2972b3be)
+
+## 7.6.0-test.1 (2026-03-12)
+
+🔧 Maintenance
+
+- Improve CI/CD workflow reliability and testing coverage [SDK] (eb86a515)
+- Update MCP server implementation for better stability [SDK] (eb86a515)
+
+📝 Documentation
+
+- Add new visual documentation for content parsing functionality [SDK] (eb86a515)
+
+## 7.6.0-test.0 (2026-03-12)
+
+## ✨ Features
+
+- Add stable/canary deployment channels with separate environments for production and development branches [API] (64542a8d)
+- Add /version API endpoint returning deployment channel information [API] (64542a8d)
+- Implement user limits and team member invitation controls [API] (6381290a)
+- Add comprehensive GitHub Copilot skills and agent documentation for AI-assisted test development [SDK] (5ff15796)
+- Add testimonials section with customer logos and quotes to marketing site [Web] (6381290a)
+- Add contact and demo pages to marketing site [Web] (6381290a)
+- Improve test environment management with better configuration and deployment workflows [Runner] (5c96e056)
+
+## 🐛 Bug Fixes
+
+- Fix environment configuration and Tailscale connectivity issues [Runner] (5c96e056)
+- Resolve Redis URL configuration problems across environments [API] (eca334be)
+- Fix Vite API endpoint configuration for proper environment targeting [Web] (bf7fdf54)
+
+## 🔧 Maintenance
+
+- Update pricing configuration and plans structure [API] (6381290a)
+- Improve deployment workflows with promotion pipelines between test, canary, and stable branches [CI/CD] (1994d769)
+- Add toast notification system for better user feedback [Web] (multiple commits)
+- Rename TestAnalytics to TestMetrics for clarity [Web] (multiple commits)
+- Remove outdated marketing articles and legal pages [Web] (6381290a)
+- Update terms of service with new date [Web] (6381290a)
+
 ## 7.5.25 (2026-03-09)
 
 ## 🐛 Bug Fixes

package/README.md

@@ -63,6 +63,7 @@ This will:
 - Create a project folder
 - Install dependencies (Vitest + TestDriver)
 - Set up your API key
+- Configure MCP for your AI assistant (VS Code, Cursor, Claude Desktop, etc.)
 - Generate an example test
 
 ### Step 3: Run Your First Test

package/agent/index.js

@@ -1918,12 +1918,12 @@ ${regression}
       const encodedData = Buffer.from(JSON.stringify(data)).toString("base64");
 
       // Build debugger URL — hosted on S3 (v7-vnc bucket)
-      const debuggerBase = process.env.TD_DEBUGGER_BASE_URL || "https://v7-vnc.s3.us-east-2.amazonaws.com";
-      const urlToOpen = `${debuggerBase}/index.html?data=${encodedData}`;
+      const debuggerBase = process.env.TD_DEBUGGER_BASE_URL || "http://v7-vnc.s3.us-east-2.amazonaws.com";
+      // URL-encode the base64 data to handle +, /, = characters safely
+      const urlToOpen = `${debuggerBase}/index.html?data=${encodeURIComponent(encodedData)}`;
 
       // Check preview mode from CLI options (SDK passes it directly)
       const previewMode = (this.cliArgs.options && this.cliArgs.options.preview) || this.config.TD_PREVIEW || "browser";
-      console.log("[DEBUG renderSandbox] preview:", previewMode);
 
       if (previewMode === "ide") {
         // Send session to VS Code extension via HTTP
@@ -1944,6 +1944,8 @@ ${regression}
     const mapping = {
       "https://api.testdriver.ai": "https://console.testdriver.ai",
       "https://v6.testdriver.ai": "https://console.testdriver.ai",
+      "https://api.canary.testdriver.ai": "https://console.canary.testdriver.ai",
+      "https://api.test.testdriver.ai": "https://console.test.testdriver.ai",
     };
     if (mapping[apiRoot]) return mapping[apiRoot];
     // Local dev: API on localhost:1337 -> Web on localhost:3001

package/agent/lib/config.js

@@ -16,12 +16,14 @@ function parseValue(value) {
   return value;
 }
 
+const channelConfig = require("../../lib/resolve-channel.js");
+
 // Factory function that creates a config instance
 const createConfig = (environment = {}) => {
   // Start with defaults
   const config = {
     TD_ANALYTICS: true,
-    TD_API_ROOT: "https://v6.testdriver.ai",
+    TD_API_ROOT: channelConfig.channels[channelConfig.active],
     TD_API_KEY: null,
     TD_PROFILE: false,
     TD_RESOLUTION: [1366, 768],

package/agent/lib/sandbox.js

@@ -511,7 +511,7 @@ const createSandbox = function (emitter, analytics, sessionInstance) {
           url = runnerVncUrl;
           logger.log(`Using runner-provided vncUrl: ${url}`);
         } else if (runnerIp && noVncPort) {
-          url = `http://${runnerIp}:${noVncPort}/vnc_lite.html`;
+          url = `http://${runnerIp}:${noVncPort}/vnc_lite.html?token=V3b8wG9`;
           logger.log(`noVNC URL constructed from runner ip+port: ${url}`);
         } else if (runnerIp) {
           url = "http://" + runnerIp;
@@ -619,7 +619,7 @@ const createSandbox = function (emitter, analytics, sessionInstance) {
         }
 
         // Construct VNC URL — use port 8080 (nginx noVNC proxy) for Windows instances
-        var directUrl = message.ip ? "http://" + message.ip + ":8080/vnc_lite.html" : undefined;
+        var directUrl = message.ip ? "http://" + message.ip + ":8080/vnc_lite.html?token=V3b8wG9" : undefined;
 
         return {
           success: true,
@@ -915,10 +915,12 @@ const createSandbox = function (emitter, analytics, sessionInstance) {
       }
 
       try {
-        if (this._cmdChannel) this._cmdChannel.detach().catch(() => {});
-        if (this._respChannel) this._respChannel.detach().catch(() => {});
-        if (this._ctrlChannel) this._ctrlChannel.detach().catch(() => {});
-        if (this._filesChannel) this._filesChannel.detach().catch(() => {});
+        await Promise.allSettled([
+          this._cmdChannel?.detach(),
+          this._respChannel?.detach(),
+          this._ctrlChannel?.detach(),
+          this._filesChannel?.detach(),
+        ].filter(Boolean));
       } catch (e) {
         /* ignore */
       }

package/ai/agents/testdriver.md

@@ -578,9 +578,6 @@ await testdriver.pressKeys(["pagedown"]);
 ### Executing Code in Sandbox
 
 ```javascript
-// JavaScript
-const result = await testdriver.exec("js", "return document.title", 5000);
-
 // Shell (Linux)
 const output = await testdriver.exec("sh", "ls -la", 5000);
 

package/ai/skills/testdriver-aws-setup/SKILL.md

@@ -369,7 +369,7 @@ You can customize the AMI to include additional software or configurations:
   <Step title="Connect via RDP">
     Use the default credentials:
     - **Username**: `testdriver`
-    - **Password**: `changemeABC123`
+    - **Password**: `wwv9uJ0sqlulbN3`
   </Step>
   
   <Step title="Change the Password">

package/ai/skills/testdriver-exec/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: testdriver:exec
-description: Execute code or shell commands in the sandbox
+description: Execute shell or PowerShell commands in the sandbox
 ---
 <!-- Generated from exec.mdx. DO NOT EDIT. -->
 
 ## Overview
 
-Execute JavaScript code in the browser or PowerShell commands in the Windows sandbox environment.
+Execute shell commands (Linux) or PowerShell commands (Windows) in the sandbox environment.
 
 ## Syntax
 
@@ -17,7 +17,7 @@ await testdriver.exec(language, code, timeout, silent)
 ## Parameters
 
 <ParamField path="language" type="string" required>
-  Language to execute: `'js'` (JavaScript) or `'pwsh'` (PowerShell)
+  Language to execute: `'sh'` (Shell/Linux) or `'pwsh'` (PowerShell/Windows)
 </ParamField>
 
 <ParamField path="code" type="string" required>
@@ -36,57 +36,40 @@ await testdriver.exec(language, code, timeout, silent)
 
 `Promise<string>` - Command output
 
-## JavaScript Execution
+## Shell Execution (Linux)
 
-Execute JavaScript in the browser context (Windows sandbox only).
+Execute shell commands in the Linux sandbox.
 
-### DOM Manipulation
+### Basic Commands
 
 ```javascript
-// Click an element via JavaScript
-await testdriver.exec('js', `
-  document.querySelector('#submit-button').click();
-`, 5000);
+// List files
+const files = await testdriver.exec('sh', 'ls -la', 5000);
 
-// Fill a form
-await testdriver.exec('js', `
-  document.querySelector('#username').value = 'testuser';
-  document.querySelector('#password').value = 'password123';
-  document.querySelector('#login-form').submit();
-`, 5000);
+// Check current directory
+const pwd = await testdriver.exec('sh', 'pwd', 5000);
 
-// Scroll to element
-await testdriver.exec('js', `
-  document.querySelector('#footer').scrollIntoView();
-`, 5000);
+// Run a script
+await testdriver.exec('sh', './setup.sh', 60000);
 ```
 
-### Reading Page Data
+### File Operations
 
 ```javascript
-// Get page title
-const title = await testdriver.exec('js', 'document.title', 5000);
-console.log('Page title:', title);
-
-// Get all links
-const links = await testdriver.exec('js', `
-  Array.from(document.querySelectorAll('a'))
-    .map(a => a.href)
-    .join('\\n')
-`, 5000);
+// Create a file
+await testdriver.exec('sh', 'echo "Hello World" > test.txt', 5000);
 
-// Check if element exists
-const exists = await testdriver.exec('js', `
-  document.querySelector('.error-message') !== null
-`, 5000);
+// Read a file
+const content = await testdriver.exec('sh', 'cat test.txt', 5000);
 
-// Get element text
-const text = await testdriver.exec('js', `
-  document.querySelector('.notification').textContent
-`, 5000);
+// Copy files
+await testdriver.exec('sh', 'cp source.txt dest.txt', 5000);
+
+// Delete files
+await testdriver.exec('sh', 'rm test.txt', 5000);
 ```
 
-## PowerShell Execution
+## PowerShell Execution (Windows)
 
 Execute PowerShell commands in the Windows sandbox.
 

package/ai/skills/testdriver-test-writer/SKILL.md

@@ -399,9 +399,6 @@ await testdriver.scrollUntilImage("Product image at bottom");
 ### Executing Code in Sandbox
 
 ```javascript
-// JavaScript
-const result = await testdriver.exec("js", "return document.title", 5000);
-
 // Shell (Linux)
 const output = await testdriver.exec("sh", "ls -la", 5000);
 

package/ai/skills/testdriver-testdriver/SKILL.md

@@ -568,9 +568,6 @@ await testdriver.pressKeys(["pagedown"]);
 ### Executing Code in Sandbox
 
 ```javascript
-// JavaScript
-const result = await testdriver.exec("js", "return document.title", 5000);
-
 // Shell (Linux)
 const output = await testdriver.exec("sh", "ls -la", 5000);
 

package/ai/skills/testdriver-wait/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: testdriver:wait
+description: Pause the execution of the script for a specified duration.
+---
+<!-- Generated from wait.mdx. DO NOT EDIT. -->
+
+## Description
+
+The `wait` method pauses test execution for a specified number of milliseconds before continuing. This is useful for adding delays between actions, waiting for animations to complete, or pausing for state changes to settle.
+
+## Syntax
+
+```javascript
+await testdriver.wait(timeout);
+```
+
+## Arguments
+
+| Argument  | Type     | Default | Description                           |
+| --------- | -------- | ------- | ------------------------------------- |
+| `timeout` | `number` | `3000`  | The duration in milliseconds to wait. |
+
+## Examples
+
+```javascript
+// Wait 2 seconds for an animation to complete
+await testdriver.find('submit button').click();
+await testdriver.wait(2000);
+
+// Wait 5 seconds
+await testdriver.wait(5000);
+
+// Wait with default timeout (3 seconds)
+await testdriver.wait();
+```
+
+## Best Practices
+
+- **Use for simple delays** — waiting for animations, transitions, or state changes after an action.
+- **Avoid for element waiting** — if you're waiting for a specific element to appear, use `find()` with a `timeout` option instead:
+  ```javascript
+  // ✅ Better for waiting for elements
+  const element = await testdriver.find('success message', { timeout: 30000 });
+
+  // ❌ Don't do this for element waiting
+  await testdriver.wait(5000);
+  const element = await testdriver.find('success message');
+  ```
+- Avoid excessively long timeouts to keep tests efficient.
+- Use sparingly — TestDriver's [redraw detection](/v7/waiting-for-elements) automatically waits for screen and network stability after each action.

package/ai/skills/testdriver-waiting-for-elements/SKILL.md

@@ -85,4 +85,6 @@ await testdriver.find('next page button').click();
 await testdriver.wait(1000);
 ```
 
-For waiting for specific **elements** to appear, prefer `find()` with a `timeout` option. Use `wait()` only for simple time-based pauses.
+<Note>
+  For waiting for specific **elements** to appear, prefer `find()` with a `timeout` option. Use `wait()` only for simple time-based pauses.
+</Note>

package/debugger/index.html

@@ -354,8 +354,21 @@
           console.error("Error parsing data:", e);
         }
       }
+      // Demo mode: use mock data if no data param provided (for local dev)
       if (!parsedData || !parsedData.url) {
-        alert("Missing or invalid data parameter.");
+        const isLocalDev = window.location.hostname === "localhost" || window.location.hostname === "127.0.0.1";
+        if (isLocalDev) {
+          console.log("[Debugger] No data param — using demo mode");
+          parsedData = {
+            url: "about:blank",
+            resolution: [1366, 768],
+            testFile: "demo-test.mjs",
+            os: "linux",
+            token: null,
+          };
+        } else {
+          alert("Missing or invalid data parameter.");
+        }
       }
 
       // Elements
@@ -402,9 +415,13 @@
         : "TestDriver";
       document.title = `${testFileName} - Debugger`;
 
-      // Embed the VNC URL in the iframe
+      // Embed the VNC URL in the iframe with token
       iframe.style.display = "block";
-      iframe.src = parsedData.url;
+      const vncUrl = new URL(parsedData.url);
+      if (parsedData.token) {
+        vncUrl.searchParams.set("token", parsedData.token);
+      }
+      iframe.src = vncUrl.toString();
 
       // Hide loading screen once iframe loads
       iframe.addEventListener("load", () => {

package/docs/docs.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://mintlify.com/docs.json",
-  "theme": "aspen",
+  "theme": "willow",
   "name": "TestDriver",
   "colors": {
     "primary": "#b3d334",

package/docs/v6/commands/exec.mdx

@@ -1,7 +1,7 @@
 ---
 title: "exec"
 sidebarTitle: "exec"
-description: "Execute custom shell or Node.js scripts within your tests."
+description: "Execute custom shell or PowerShell scripts within your tests."
 icon: "code"
 mode: "wide"
 ---
@@ -14,49 +14,43 @@ import Example from "/snippets/tests/exec-shell-yaml.mdx";
 
 ## Description
 
-The `exec` command allows you to execute custom Node.js scripts within your TestDriver tests. This is useful for tasks like generating dynamic data, interacting with APIs, or performing custom logic during a test. The output of the script can be stored in a variable for use in subsequent steps. It's important to note that the output from `exec` must be a `string`.
+The `exec` command allows you to execute shell commands (Linux) or PowerShell commands (Windows) within your TestDriver tests. This is useful for launching applications, file operations, or performing system commands during a test.
 
 ## Arguments
 
 | Argument |   Type   | Description                                                                                                                                                                        |
 | :------: | :------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  `lang`  | `string` | The language of the script to execute. Supported values are `pwsh` and `js`.                                                                                                       |
+|  `lang`  | `string` | The language of the script to execute. Supported values are `sh` (Shell/Linux) or `pwsh` (PowerShell/Windows).                                                                     |
 | `output` | `string` | The variable name to store the result of the script. This variable can be accessed as `${OUTPUT.<var>}` in future steps.                                                           |
-|  `code`  | `string` | The script to execute on Windows systems. For `js`, the script must define the output as `result`.                                                                                 |
+|  `code`  | `string` | The script to execute.                                                                                                                                                             |
 | `silent` | `string` | Defaults to `false`. The command will print the output of the script. This is useful for suppressing unnecessary or private output in the test logs and it's useful for debugging. |
 
 ## Example usage
 
-This example demonstrates how to use the `exec` command to generate a TOTP (Time-based One-Time Password) using the `totp-generator` library.
+This example demonstrates how to use the `exec` command to launch a calculator application.
 
-```yaml otp-generator.yaml
+```yaml calculator.yaml
 version: 6.0.0
 steps:
   - commands:
       - command: exec
         lang: pwsh
         code: |
-          npm install totp-generator
-      - command: exec
-        lang: js
-        output: totp
-        code: |
-          const { TOTP } = require("totp-generator");
-          let otp = TOTP.generate("JBSWY3DPEB3W64TMMQQQ").otp;
-          console.log(otp);
-          result = otp;
-      - command: type
-        text: ${OUTPUT.totp}
+          start /B calc.exe
+          timeout /t 5
+      - command: wait-for-text
+        text: "calculator"
+        timeout: 30000
 ```
 
 ## Additional details
 
-- Supported `lang` values are `js` or `pwsh`:
-  - `js` code is executed in a Node.js [VM](https://nodejs.org/api/vm.html) internally on the host machine (for example the machine where your CI/CD runs, or your computer if using the local agent).
-  - `pwsh` code is executed in the shell on target runner (which can be the cloud runner, local sandbox, or local machine, depending on where you run your tests).
+- Supported `lang` values are `sh` or `pwsh`:
+  - `sh` code is executed in the shell on Linux sandboxes.
+  - `pwsh` code is executed in PowerShell on Windows sandboxes.
     - **Note:** You can also use `pwsh` in [lifecycle](/guide/lifecycle) scripts to install npm packages if you need them.
     - Otherwise, the `pwsh` code can be used within test steps to launch applications or perform simple commands (like writing text to a file on the machine to perform a simple file upload).
-- The `output`argument is assigned automatically by setting `result = somestringvalue` in the script you run.
+- The `output` argument captures stdout from your script.
 
 ## Protips
 

package/docs/v7/_drafts/agents.mdx

@@ -372,20 +372,11 @@ await testdriver.scrollUntilText('Footer', 'down', 5000);
 
 ### exec(language, code, timeout, silent) - Execute Code
 
-Execute JavaScript or PowerShell in the sandbox.
+Execute shell or PowerShell in the sandbox.
 
 ```javascript
-// JavaScript execution (in browser)
-const title = await testdriver.exec('js', 'document.title', 5000);
-
-await testdriver.exec('js', `
-  document.querySelector('#username').value = 'testuser';
-`, 5000);
-
-// Get element text
-const text = await testdriver.exec('js', `
-  document.querySelector('.notification').textContent
-`, 5000);
+// Shell execution (Linux sandbox)
+const output = await testdriver.exec('sh', 'ls -la', 5000);
 
 // PowerShell execution (Windows sandbox)
 await testdriver.exec('pwsh', 'npm install -g http-server', 30000);
@@ -843,7 +834,7 @@ Using explicit sandboxes provides:
 | `assert(text)` | Verify state | `await testdriver.assert('button is visible')` |
 | `pressKeys(keys)` | Keyboard shortcuts | `await testdriver.pressKeys(['ctrl', 'c'])` |
 | `scroll(dir, amt)` | Scroll page | `await testdriver.scroll('down', 500)` |
-| `exec(lang, code)` | Execute code | `await testdriver.exec('js', 'document.title', 5000)` |
+| `exec(lang, code)` | Execute code | `await testdriver.exec('sh', 'ls -la', 5000)` |
 | `connect(opts)` | Connect to sandbox | `await testdriver.connect({ sandboxId: 'i-123' })` |
 | `disconnect()` | Close connection | `await testdriver.disconnect()` |
 

package/docs/v7/_drafts/commands/exec.mdx

@@ -1,7 +1,7 @@
 ---
 title: "exec"
 sidebarTitle: "exec"
-description: "Execute custom shell or Node.js scripts within your tests."
+description: "Execute custom shell or PowerShell scripts within your tests."
 icon: "code"
 mode: "wide"
 ---
@@ -14,49 +14,43 @@ import Example from "/snippets/tests/exec-shell-yaml.mdx";
 
 ## Description
 
-The `exec` command allows you to execute custom Node.js scripts within your TestDriver tests. This is useful for tasks like generating dynamic data, interacting with APIs, or performing custom logic during a test. The output of the script can be stored in a variable for use in subsequent steps. It's important to note that the output from `exec` must be a `string`.
+The `exec` command allows you to execute shell commands (Linux) or PowerShell commands (Windows) within your TestDriver tests. This is useful for launching applications, file operations, or performing system commands during a test.
 
 ## Arguments
 
 | Argument |   Type   | Description                                                                                                                                                                        |
 | :------: | :------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  `lang`  | `string` | The language of the script to execute. Supported values are `pwsh` and `js`.                                                                                                       |
+|  `lang`  | `string` | The language of the script to execute. Supported values are `sh` (Shell/Linux) or `pwsh` (PowerShell/Windows).                                                                     |
 | `output` | `string` | The variable name to store the result of the script. This variable can be accessed as `${OUTPUT.<var>}` in future steps.                                                           |
-|  `code`  | `string` | The script to execute on Windows systems. For `js`, the script must define the output as `result`.                                                                                 |
+|  `code`  | `string` | The script to execute.                                                                                                                                                             |
 | `silent` | `string` | Defaults to `false`. The command will print the output of the script. This is useful for suppressing unnecessary or private output in the test logs and it's useful for debugging. |
 
 ## Example usage
 
-This example demonstrates how to use the `exec` command to generate a TOTP (Time-based One-Time Password) using the `totp-generator` library.
+This example demonstrates how to use the `exec` command to launch a calculator application.
 
-```yaml otp-generator.yaml
+```yaml calculator.yaml
 version: 6.0.0
 steps:
   - commands:
       - command: exec
         lang: pwsh
         code: |
-          npm install totp-generator
-      - command: exec
-        lang: js
-        output: totp
-        code: |
-          const { TOTP } = require("totp-generator");
-          let otp = TOTP.generate("JBSWY3DPEB3W64TMMQQQ").otp;
-          console.log(otp);
-          result = otp;
-      - command: type
-        text: ${OUTPUT.totp}
+          start /B calc.exe
+          timeout /t 5
+      - command: wait-for-text
+        text: "calculator"
+        timeout: 30000
 ```
 
 ## Additional details
 
-- Supported `lang` values are `js` or `pwsh`:
-  - `js` code is executed in a Node.js [VM](https://nodejs.org/api/vm.html) internally on the host machine (for example the machine where your CI/CD runs, or your computer if using the local agent).
-  - `pwsh` code is executed in the shell on target runner (which can be the cloud runner, local sandbox, or local machine, depending on where you run your tests).
+- Supported `lang` values are `sh` or `pwsh`:
+  - `sh` code is executed in the shell on Linux sandboxes.
+  - `pwsh` code is executed in PowerShell on Windows sandboxes.
     - **Note:** You can also use `pwsh` in [lifecycle](/guide/lifecycle) scripts to install npm packages if you need them.
     - Otherwise, the `pwsh` code can be used within test steps to launch applications or perform simple commands (like writing text to a file on the machine to perform a simple file upload).
-- The `output`argument is assigned automatically by setting `result = somestringvalue` in the script you run.
+- The `output` argument captures stdout from your script.
 
 ## Protips
 

package/docs/v7/aws-setup.mdx

@@ -370,7 +370,7 @@ You can customize the AMI to include additional software or configurations:
   <Step title="Connect via RDP">
     Use the default credentials:
     - **Username**: `testdriver`
-    - **Password**: `changemeABC123`
+    - **Password**: `wwv9uJ0sqlulbN3`
   </Step>
   
   <Step title="Change the Password">