From eb2ae3343340a2815496b2e8e1cc42edb26459e6 Mon Sep 17 00:00:00 2001 From: Yazan-O <154028854+Yazan-O@users.noreply.github.com> Date: Fri, 24 Jul 2026 09:24:23 -0500 Subject: [PATCH] docs(mcp): correct bootstrap tool name and pathname parameter The MCP server registers testsprite_bootstrap (parameter pathname), not testsprite_bootstrap_tests (parameter path). Align the docs across the six referencing files. Verified via an MCP tools/list on @testsprite/testsprite-mcp 0.0.39. --- mcp/concepts/key-terms.mdx | 2 +- mcp/core/create-tests-new-feature.mdx | 4 ++-- mcp/core/create-tests-new-project.mdx | 4 ++-- mcp/core/tools.mdx | 8 ++++---- mcp/maintenance/cost-performance.mdx | 2 +- mcp/troubleshooting/application-detection-issues.mdx | 2 +- 6 files changed, 11 insertions(+), 11 deletions(-) diff --git a/mcp/concepts/key-terms.mdx b/mcp/concepts/key-terms.mdx index 1baa170..c94ad74 100644 --- a/mcp/concepts/key-terms.mdx +++ b/mcp/concepts/key-terms.mdx @@ -206,7 +206,7 @@ TestSprite offers two scope options to balance between comprehensive coverage an | Speed | Takes longer | Fast feedback | | Coverage | Full coverage | Recent changes only | -Set the scope in the bootstrapping page when you call the `testsprite_bootstrap_tests` tool. +Set the scope in the bootstrapping page when you call the `testsprite_bootstrap` tool. Learn more about TestSprite MCP tools and commands diff --git a/mcp/core/create-tests-new-feature.mdx b/mcp/core/create-tests-new-feature.mdx index 416005e..c5305fb 100644 --- a/mcp/core/create-tests-new-feature.mdx +++ b/mcp/core/create-tests-new-feature.mdx @@ -36,7 +36,7 @@ flowchart LR ### Step 1: Bootstrap with Diff Scope -The AI calls `testsprite_bootstrap_tests` with `testScope: "diff"` to initialize testing for changed code only. +The AI calls `testsprite_bootstrap` with `testScope: "diff"` to initialize testing for changed code only. diff @@ -61,7 +61,7 @@ The AI calls `testsprite_bootstrap_tests` with `testScope: "diff"` to initialize ```javascript Configuration expandable -testsprite_bootstrap_tests({ +testsprite_bootstrap({ localPort: 5173, // or your port type: "frontend", // or "backend" projectPath: "/absolute/path/to/your/project", diff --git a/mcp/core/create-tests-new-project.mdx b/mcp/core/create-tests-new-project.mdx index e176c8b..104b25d 100644 --- a/mcp/core/create-tests-new-project.mdx +++ b/mcp/core/create-tests-new-project.mdx @@ -46,7 +46,7 @@ flowchart LR ### Step 1: Bootstrap Testing Environment -The AI calls `testsprite_bootstrap_tests` to initialize the testing environment. +The AI calls `testsprite_bootstrap` to initialize the testing environment. Learn more about bootstrap configuration: [First Test: Configuration](/mcp/getting-started/first-test#step-3%3A-configuration-required) @@ -62,7 +62,7 @@ The AI calls `testsprite_bootstrap_tests` to initialize the testing environment. ```javascript Configuration expandable -testsprite_bootstrap_tests({ +testsprite_bootstrap({ localPort: 5173, // or your port type: "frontend", // or "backend" projectPath: "/absolute/path/to/your/project", diff --git a/mcp/core/tools.mdx b/mcp/core/tools.mdx index dd367a4..c1cdb9d 100644 --- a/mcp/core/tools.mdx +++ b/mcp/core/tools.mdx @@ -7,19 +7,19 @@ icon: "wrench" ## Core Tools TestSprite MCP Server provides **8 core tools** that work together to deliver comprehensive automated testing. Your AI assistant uses these tools automatically when you request testing. - + **Purpose:** Initialize testing environment and configuration **Parameters:** - `localPort` (number): Port where your application is running (default: 5173) - - `path` (string): Specifies a path you want to test directly, which isn’t accessible through navigation from other pages. + - `pathname` (string): Specifies a path you want to test directly, which isn’t accessible through navigation from other pages. - `type` (string): Project type - "frontend" or "backend" - `projectPath` (string): Absolute path to your project directory - `testScope` (string): Testing scope - "codebase" or "diff" **Usage:** ```javascript expandable - testsprite_bootstrap_tests({ + testsprite_bootstrap({ localPort: 3000, type: "frontend", projectPath: "/Users/dev/my-project", @@ -254,7 +254,7 @@ The tools work together in a specific sequence following the complete TestSprite ```mermaid graph TD - A[testsprite_bootstrap_tests] --> B[Read User PRD] + A[testsprite_bootstrap] --> B[Read User PRD] B --> C[testsprite_generate_code_summary] C --> D[testsprite_generate_standardized_prd] D --> E{Project Type?} diff --git a/mcp/maintenance/cost-performance.mdx b/mcp/maintenance/cost-performance.mdx index 2eeeb26..616e863 100644 --- a/mcp/maintenance/cost-performance.mdx +++ b/mcp/maintenance/cost-performance.mdx @@ -30,7 +30,7 @@ Common code patterns for efficient test execution and cost optimization. Use the ```javascript Diff-only execution -testsprite_bootstrap_tests({ testScope: "diff", ... }) +testsprite_bootstrap({ testScope: "diff", ... }) ``` ```javascript Subset during iteration testsprite_generate_code_and_execute({ testIds: ["TC005", "TC010"] }) diff --git a/mcp/troubleshooting/application-detection-issues.mdx b/mcp/troubleshooting/application-detection-issues.mdx index 3218dbb..00d2ec2 100644 --- a/mcp/troubleshooting/application-detection-issues.mdx +++ b/mcp/troubleshooting/application-detection-issues.mdx @@ -54,7 +54,7 @@ If you experience issues where **TestSprite can't access your running applicatio ``` Update bootstrap call ```bash expandable - testsprite_bootstrap_tests ({ + testsprite_bootstrap ({ localPort: 3000, // Use actual port type: "frontend", projectPath: "/path/to/project",