Skip to content

docs(mcp): fix MCP tool name testsprite_bootstrap_tests -> testsprite_bootstrap #59

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Yazan-O wants to merge 1 commit into
base: v1.0
Choose a base branch
from
Open

docs(mcp): fix MCP tool name testsprite_bootstrap_tests -> testsprite_bootstrap #59

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion mcp/concepts/key-terms.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 |

<Info>Set the scope in the bootstrapping page when you call the `testsprite_bootstrap_tests` tool. </Info>
<Info>Set the scope in the bootstrapping page when you call the `testsprite_bootstrap` tool. </Info>

<Card title="MCP Tools Reference" href="/mcp/core/tools" icon="wrench">
Learn more about TestSprite MCP tools and commands
Expand Down
4 changes: 2 additions & 2 deletions mcp/core/create-tests-new-feature.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<Frame>
<img src="../../images/bootstrap-diff.png" alt="diff" />
Expand All @@ -61,7 +61,7 @@ The AI calls `testsprite_bootstrap_tests` with `testScope: "diff"` to initialize

<CodeGroup>
```javascript Configuration expandable
testsprite_bootstrap_tests({
testsprite_bootstrap({
localPort: 5173, // or your port
type: "frontend", // or "backend"
projectPath: "/absolute/path/to/your/project",
Expand Down
4 changes: 2 additions & 2 deletions mcp/core/create-tests-new-project.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<Info>Learn more about bootstrap configuration: [First Test: Configuration](/mcp/getting-started/first-test#step-3%3A-configuration-required)</Info>

Expand All @@ -62,7 +62,7 @@ The AI calls `testsprite_bootstrap_tests` to initialize the testing environment.

<CodeGroup>
```javascript Configuration expandable
testsprite_bootstrap_tests({
testsprite_bootstrap({
localPort: 5173, // or your port
type: "frontend", // or "backend"
projectPath: "/absolute/path/to/your/project",
Expand Down
8 changes: 4 additions & 4 deletions mcp/core/tools.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
<AccordionGroup>
<Accordion title="testsprite_bootstrap_tests">
<Accordion title="testsprite_bootstrap">
**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",
Expand Down Expand Up @@ -254,7 +254,7 @@ The tools work together in a specific sequence following the complete TestSprite
<Card>
```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?}
Expand Down
2 changes: 1 addition & 1 deletion mcp/maintenance/cost-performance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Common code patterns for efficient test execution and cost optimization. Use the

<CodeGroup>
```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"] })
Expand Down
2 changes: 1 addition & 1 deletion mcp/troubleshooting/application-detection-issues.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand Down