@testdriverai/mcp 7.11.185-test → 7.11.186-test
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/ai/skills/testdriver-mcp-setup/SKILL.md +191 -0
- package/ai/skills/testdriver-quickstart/SKILL.md +2 -2
- package/ai/skills/testdriver-quickstart-manual/SKILL.md +2 -2
- package/ai/skills/testdriver-self-hosted/SKILL.md +4 -0
- package/docs/docs.json +6 -2
- package/docs/mcp-setup.mdx +192 -0
- package/docs/quickstart-manual.mdx +2 -2
- package/docs/quickstart.mdx +2 -2
- package/package.json +1 -1
- package/ai/skills/testdriver-quickstart-cli/SKILL.md +0 -436
- package/docs/quickstart-cli.mdx +0 -437
|
@@ -0,0 +1,191 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: testdriver:mcp-setup
|
|
3
|
+
description: Connect any AI client to TestDriver by adding one URL.
|
|
4
|
+
---
|
|
5
|
+
<!-- Generated from mcp-setup.mdx. DO NOT EDIT. -->
|
|
6
|
+
|
|
7
|
+
TestDriver runs a hosted [Model Context Protocol](https://modelcontextprotocol.io) server. There is nothing to install and no API key to paste. Add one URL to your AI client, sign in through the browser, and the computer-use tools appear in chat.
|
|
8
|
+
|
|
9
|
+
```text
|
|
10
|
+
https://mcp.testdriver.ai/mcp
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
<Info>
|
|
14
|
+
**Prerequisites**
|
|
15
|
+
|
|
16
|
+
- An MCP-compatible AI client (Claude, Claude Code, VS Code, Cursor, ChatGPT, and others)
|
|
17
|
+
- A TestDriver account. [Create one for free](https://console.testdriver.ai/settings). You get 60 device minutes, no credit card required.
|
|
18
|
+
</Info>
|
|
19
|
+
|
|
20
|
+
## Add the server
|
|
21
|
+
|
|
22
|
+
Most clients accept the URL directly. Pick yours below.
|
|
23
|
+
|
|
24
|
+
<Tabs>
|
|
25
|
+
<Tab title="Claude">
|
|
26
|
+
1. Open **Settings → Connectors → Add custom connector**.
|
|
27
|
+
2. Paste `https://mcp.testdriver.ai/mcp`.
|
|
28
|
+
3. Click **Connect** and sign in with TestDriver when the browser opens.
|
|
29
|
+
</Tab>
|
|
30
|
+
|
|
31
|
+
<Tab title="Claude Code">
|
|
32
|
+
```bash
|
|
33
|
+
claude mcp add --transport http testdriver https://mcp.testdriver.ai/mcp
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
Run `/mcp` in a session to start the browser login and confirm the tools are connected.
|
|
37
|
+
</Tab>
|
|
38
|
+
|
|
39
|
+
<Tab title="VS Code">
|
|
40
|
+
Add this to `.vscode/mcp.json` in your project. VS Code uses the `servers` key:
|
|
41
|
+
|
|
42
|
+
```json .vscode/mcp.json
|
|
43
|
+
{
|
|
44
|
+
"servers": {
|
|
45
|
+
"testdriver": {
|
|
46
|
+
"type": "http",
|
|
47
|
+
"url": "https://mcp.testdriver.ai/mcp"
|
|
48
|
+
}
|
|
49
|
+
}
|
|
50
|
+
}
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
VS Code prompts you to authorize the server the first time you use it.
|
|
54
|
+
</Tab>
|
|
55
|
+
|
|
56
|
+
<Tab title="Cursor">
|
|
57
|
+
Add this to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):
|
|
58
|
+
|
|
59
|
+
```json .cursor/mcp.json
|
|
60
|
+
{
|
|
61
|
+
"mcpServers": {
|
|
62
|
+
"testdriver": {
|
|
63
|
+
"url": "https://mcp.testdriver.ai/mcp"
|
|
64
|
+
}
|
|
65
|
+
}
|
|
66
|
+
}
|
|
67
|
+
```
|
|
68
|
+
</Tab>
|
|
69
|
+
|
|
70
|
+
<Tab title="ChatGPT">
|
|
71
|
+
1. Open **Settings → Connectors → Create**.
|
|
72
|
+
2. Paste `https://mcp.testdriver.ai/mcp` as the MCP server URL.
|
|
73
|
+
3. Choose OAuth for authentication and sign in with TestDriver.
|
|
74
|
+
</Tab>
|
|
75
|
+
|
|
76
|
+
<Tab title="Other clients">
|
|
77
|
+
Any spec-compliant client works. Point it at the URL using the streamable HTTP transport:
|
|
78
|
+
|
|
79
|
+
```json
|
|
80
|
+
{
|
|
81
|
+
"mcpServers": {
|
|
82
|
+
"testdriver": {
|
|
83
|
+
"url": "https://mcp.testdriver.ai/mcp"
|
|
84
|
+
}
|
|
85
|
+
}
|
|
86
|
+
}
|
|
87
|
+
```
|
|
88
|
+
</Tab>
|
|
89
|
+
</Tabs>
|
|
90
|
+
|
|
91
|
+
<Note>
|
|
92
|
+
Clients disagree on the top-level key. VS Code uses `servers`, most others use `mcpServers`, Zed uses `context_servers`, and Codex uses TOML `[mcp_servers]`. If the tools do not show up, check the key before anything else.
|
|
93
|
+
</Note>
|
|
94
|
+
|
|
95
|
+
## Sign in
|
|
96
|
+
|
|
97
|
+
The server speaks OAuth 2.1 and advertises its authorization server via [RFC 9728](https://www.rfc-editor.org/rfc/rfc9728) protected-resource metadata:
|
|
98
|
+
|
|
99
|
+
```text
|
|
100
|
+
https://mcp.testdriver.ai/.well-known/oauth-protected-resource
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
Spec-compliant clients read that metadata, open a browser, and complete the handshake for you. Every tool is scoped to the team you sign in with.
|
|
104
|
+
|
|
105
|
+
## Verify it works
|
|
106
|
+
|
|
107
|
+
Ask your client to drive a browser:
|
|
108
|
+
|
|
109
|
+
```text
|
|
110
|
+
Use TestDriver to open example.com and assert the page title is visible.
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
The agent starts a sandbox and returns a screenshot with every action. Each connection gets its own isolated sandbox, so multiple people and multiple chats can run tests at the same time without interfering.
|
|
114
|
+
|
|
115
|
+
## What you get
|
|
116
|
+
|
|
117
|
+
The hosted server exposes the full live tool set:
|
|
118
|
+
|
|
119
|
+
| Tool | Purpose |
|
|
120
|
+
| --- | --- |
|
|
121
|
+
| `session_start`, `session_status`, `session_extend` | Start a sandbox, check its health, add more time |
|
|
122
|
+
| `find`, `findall`, `find_and_click` | Locate elements by plain-English description |
|
|
123
|
+
| `click`, `hover`, `type`, `press_keys`, `scroll` | Perform actions |
|
|
124
|
+
| `assert`, `check` | Ask yes/no questions about the screen |
|
|
125
|
+
| `screenshot`, `exec`, `wait`, `focus_application` | Capture state, run commands, pause |
|
|
126
|
+
|
|
127
|
+
Every action also returns the SDK code for that step, so the agent can write a runnable [Vitest](https://vitest.dev) test as it goes.
|
|
128
|
+
|
|
129
|
+
## Local server for CI and automation
|
|
130
|
+
|
|
131
|
+
For headless automation, or when you would rather use an API key than a browser login, run the server as a local stdio process:
|
|
132
|
+
|
|
133
|
+
```bash
|
|
134
|
+
npx -p testdriverai testdriverai-mcp
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
It reads `TD_API_KEY` from the environment. Generate a key at [console.testdriver.ai/settings](https://console.testdriver.ai/settings).
|
|
138
|
+
|
|
139
|
+
```json
|
|
140
|
+
{
|
|
141
|
+
"mcpServers": {
|
|
142
|
+
"testdriver": {
|
|
143
|
+
"type": "stdio",
|
|
144
|
+
"command": "npx",
|
|
145
|
+
"args": ["-p", "testdriverai", "testdriverai-mcp"],
|
|
146
|
+
"env": { "TD_API_KEY": "${TD_API_KEY}" }
|
|
147
|
+
}
|
|
148
|
+
}
|
|
149
|
+
}
|
|
150
|
+
```
|
|
151
|
+
|
|
152
|
+
<Tip>
|
|
153
|
+
`npx testdriverai init` writes this config for you, plus the TestDriver agent, skills, an example test, and a GitHub Actions workflow. See [Setting up your workspace](/quickstart-manual).
|
|
154
|
+
</Tip>
|
|
155
|
+
|
|
156
|
+
## Troubleshooting
|
|
157
|
+
|
|
158
|
+
<AccordionGroup>
|
|
159
|
+
<Accordion title="The tools do not appear in my client">
|
|
160
|
+
Confirm the URL is exactly `https://mcp.testdriver.ai/mcp`, check that you used the correct top-level config key for your client, and restart the client. Most clients read their MCP config only at startup.
|
|
161
|
+
</Accordion>
|
|
162
|
+
|
|
163
|
+
<Accordion title="The browser login never completes">
|
|
164
|
+
Your client must support OAuth 2.1 with Dynamic Client Registration. Older clients, and clients that only support stdio servers, cannot connect to the hosted URL. Use the local server with `TD_API_KEY` instead.
|
|
165
|
+
</Accordion>
|
|
166
|
+
|
|
167
|
+
<Accordion title="I ran out of device minutes">
|
|
168
|
+
Sandbox time is billed per minute. Check your usage and plan at [console.testdriver.ai](https://console.testdriver.ai).
|
|
169
|
+
</Accordion>
|
|
170
|
+
|
|
171
|
+
<Accordion title="The sandbox expired mid-session">
|
|
172
|
+
Sessions time out after a period of inactivity. Ask the agent to call `session_extend` before it expires, or `session_start` to get a fresh sandbox.
|
|
173
|
+
</Accordion>
|
|
174
|
+
</AccordionGroup>
|
|
175
|
+
|
|
176
|
+
## Next steps
|
|
177
|
+
|
|
178
|
+
<CardGroup cols={2}>
|
|
179
|
+
<Card title="Generating tests" icon="wand-magic-sparkles" href="/generating-tests" arrow horizontal>
|
|
180
|
+
Prompting patterns that get the best tests out of the agent.
|
|
181
|
+
</Card>
|
|
182
|
+
<Card title="Setting up your workspace" icon="wrench" href="/quickstart-manual" arrow horizontal>
|
|
183
|
+
Add the SDK to a project so generated tests run locally and in CI.
|
|
184
|
+
</Card>
|
|
185
|
+
<Card title="Walkthrough" icon="map" href="/provision" arrow horizontal>
|
|
186
|
+
Provision apps, locate elements, perform actions, and make assertions.
|
|
187
|
+
</Card>
|
|
188
|
+
<Card title="CI/CD" icon="circle-play" href="/ci-cd" arrow horizontal>
|
|
189
|
+
Run your tests on every pull request.
|
|
190
|
+
</Card>
|
|
191
|
+
</CardGroup>
|
|
@@ -10,8 +10,8 @@ TestDriver writes and runs computer-use tests for web apps, desktop apps, and br
|
|
|
10
10
|
<Card title="Add to GitHub" icon="github" href="/quickstart-github" arrow horizontal>
|
|
11
11
|
No install. Mention `@testdriverai` in a PR or issue and it writes, runs, and commits tests for you.
|
|
12
12
|
</Card>
|
|
13
|
-
<Card title="
|
|
14
|
-
|
|
13
|
+
<Card title="MCP Setup" icon="plug" href="/mcp-setup" arrow horizontal>
|
|
14
|
+
Add one URL to Claude, Cursor, VS Code, ChatGPT, or any MCP client. No install, no API key.
|
|
15
15
|
</Card>
|
|
16
16
|
<Card title="Manual" icon="wrench" href="/quickstart-manual" arrow horizontal>
|
|
17
17
|
Add TestDriver to an existing Vitest project file by file.
|
|
@@ -7,7 +7,7 @@ description: Add TestDriver to an existing project by hand.
|
|
|
7
7
|
Add TestDriver to an existing project without the `init` scaffold. This is useful when you already have a Vitest setup or want full control over each file.
|
|
8
8
|
|
|
9
9
|
<Tip>
|
|
10
|
-
If you
|
|
10
|
+
If you only want to drive TestDriver from chat, [MCP Setup](/mcp-setup) is a single URL with nothing to install.
|
|
11
11
|
</Tip>
|
|
12
12
|
|
|
13
13
|
<Steps>
|
|
@@ -120,7 +120,7 @@ If you want to write tests with an AI assistant, connect the TestDriver agent an
|
|
|
120
120
|
npx testdriverai init --client cursor,claude-code,vscode --no-sample-test
|
|
121
121
|
```
|
|
122
122
|
|
|
123
|
-
See [
|
|
123
|
+
See [MCP Setup](/mcp-setup) for the configuration of each client.
|
|
124
124
|
|
|
125
125
|
## Next steps
|
|
126
126
|
|
|
@@ -44,6 +44,10 @@ Run test sandboxes on your AWS infrastructure while using TestDriver's hosted da
|
|
|
44
44
|
- **Your AI keys** — control costs with your own OpenAI, Anthropic, or other provider
|
|
45
45
|
- **Custom AMIs** — install specific software, configure networking
|
|
46
46
|
|
|
47
|
+
<Note>
|
|
48
|
+
**Bring your own Gemini API key.** TestDriver uses Google Gemini for vision and reasoning. When supplying your own Gemini key, it must be a [Gemini Enterprise Agent Platform express mode API key](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/start/api-keys?usertype=expressmode) — standard Google AI Studio (Generative Language API) keys are not supported for self-hosted deployments.
|
|
49
|
+
</Note>
|
|
50
|
+
|
|
47
51
|
<Card
|
|
48
52
|
title="AWS Setup Guide"
|
|
49
53
|
icon="aws"
|
package/docs/docs.json
CHANGED
|
@@ -23,7 +23,7 @@
|
|
|
23
23
|
"icon": "rocket",
|
|
24
24
|
"pages": [
|
|
25
25
|
"/quickstart-github",
|
|
26
|
-
"/
|
|
26
|
+
"/mcp-setup"
|
|
27
27
|
]
|
|
28
28
|
},
|
|
29
29
|
{
|
|
@@ -181,7 +181,11 @@
|
|
|
181
181
|
},
|
|
182
182
|
{
|
|
183
183
|
"source": "/quickstart-ai-setup",
|
|
184
|
-
"destination": "/
|
|
184
|
+
"destination": "/mcp-setup"
|
|
185
|
+
},
|
|
186
|
+
{
|
|
187
|
+
"source": "/quickstart-cli",
|
|
188
|
+
"destination": "/mcp-setup"
|
|
185
189
|
},
|
|
186
190
|
{
|
|
187
191
|
"source": "/v7/ai",
|
|
@@ -0,0 +1,192 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: "MCP Setup"
|
|
3
|
+
sidebarTitle: "MCP Setup"
|
|
4
|
+
description: "Connect any AI client to TestDriver by adding one URL."
|
|
5
|
+
icon: "plug"
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
TestDriver runs a hosted [Model Context Protocol](https://modelcontextprotocol.io) server. There is nothing to install and no API key to paste. Add one URL to your AI client, sign in through the browser, and the computer-use tools appear in chat.
|
|
9
|
+
|
|
10
|
+
```text
|
|
11
|
+
https://mcp.testdriver.ai/mcp
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
<Info>
|
|
15
|
+
**Prerequisites**
|
|
16
|
+
|
|
17
|
+
- An MCP-compatible AI client (Claude, Claude Code, VS Code, Cursor, ChatGPT, and others)
|
|
18
|
+
- A TestDriver account. [Create one for free](https://console.testdriver.ai/settings). You get 60 device minutes, no credit card required.
|
|
19
|
+
</Info>
|
|
20
|
+
|
|
21
|
+
## Add the server
|
|
22
|
+
|
|
23
|
+
Most clients accept the URL directly. Pick yours below.
|
|
24
|
+
|
|
25
|
+
<Tabs>
|
|
26
|
+
<Tab title="Claude">
|
|
27
|
+
1. Open **Settings → Connectors → Add custom connector**.
|
|
28
|
+
2. Paste `https://mcp.testdriver.ai/mcp`.
|
|
29
|
+
3. Click **Connect** and sign in with TestDriver when the browser opens.
|
|
30
|
+
</Tab>
|
|
31
|
+
|
|
32
|
+
<Tab title="Claude Code">
|
|
33
|
+
```bash
|
|
34
|
+
claude mcp add --transport http testdriver https://mcp.testdriver.ai/mcp
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
Run `/mcp` in a session to start the browser login and confirm the tools are connected.
|
|
38
|
+
</Tab>
|
|
39
|
+
|
|
40
|
+
<Tab title="VS Code">
|
|
41
|
+
Add this to `.vscode/mcp.json` in your project. VS Code uses the `servers` key:
|
|
42
|
+
|
|
43
|
+
```json .vscode/mcp.json
|
|
44
|
+
{
|
|
45
|
+
"servers": {
|
|
46
|
+
"testdriver": {
|
|
47
|
+
"type": "http",
|
|
48
|
+
"url": "https://mcp.testdriver.ai/mcp"
|
|
49
|
+
}
|
|
50
|
+
}
|
|
51
|
+
}
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
VS Code prompts you to authorize the server the first time you use it.
|
|
55
|
+
</Tab>
|
|
56
|
+
|
|
57
|
+
<Tab title="Cursor">
|
|
58
|
+
Add this to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):
|
|
59
|
+
|
|
60
|
+
```json .cursor/mcp.json
|
|
61
|
+
{
|
|
62
|
+
"mcpServers": {
|
|
63
|
+
"testdriver": {
|
|
64
|
+
"url": "https://mcp.testdriver.ai/mcp"
|
|
65
|
+
}
|
|
66
|
+
}
|
|
67
|
+
}
|
|
68
|
+
```
|
|
69
|
+
</Tab>
|
|
70
|
+
|
|
71
|
+
<Tab title="ChatGPT">
|
|
72
|
+
1. Open **Settings → Connectors → Create**.
|
|
73
|
+
2. Paste `https://mcp.testdriver.ai/mcp` as the MCP server URL.
|
|
74
|
+
3. Choose OAuth for authentication and sign in with TestDriver.
|
|
75
|
+
</Tab>
|
|
76
|
+
|
|
77
|
+
<Tab title="Other clients">
|
|
78
|
+
Any spec-compliant client works. Point it at the URL using the streamable HTTP transport:
|
|
79
|
+
|
|
80
|
+
```json
|
|
81
|
+
{
|
|
82
|
+
"mcpServers": {
|
|
83
|
+
"testdriver": {
|
|
84
|
+
"url": "https://mcp.testdriver.ai/mcp"
|
|
85
|
+
}
|
|
86
|
+
}
|
|
87
|
+
}
|
|
88
|
+
```
|
|
89
|
+
</Tab>
|
|
90
|
+
</Tabs>
|
|
91
|
+
|
|
92
|
+
<Note>
|
|
93
|
+
Clients disagree on the top-level key. VS Code uses `servers`, most others use `mcpServers`, Zed uses `context_servers`, and Codex uses TOML `[mcp_servers]`. If the tools do not show up, check the key before anything else.
|
|
94
|
+
</Note>
|
|
95
|
+
|
|
96
|
+
## Sign in
|
|
97
|
+
|
|
98
|
+
The server speaks OAuth 2.1 and advertises its authorization server via [RFC 9728](https://www.rfc-editor.org/rfc/rfc9728) protected-resource metadata:
|
|
99
|
+
|
|
100
|
+
```text
|
|
101
|
+
https://mcp.testdriver.ai/.well-known/oauth-protected-resource
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
Spec-compliant clients read that metadata, open a browser, and complete the handshake for you. Every tool is scoped to the team you sign in with.
|
|
105
|
+
|
|
106
|
+
## Verify it works
|
|
107
|
+
|
|
108
|
+
Ask your client to drive a browser:
|
|
109
|
+
|
|
110
|
+
```text
|
|
111
|
+
Use TestDriver to open example.com and assert the page title is visible.
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
The agent starts a sandbox and returns a screenshot with every action. Each connection gets its own isolated sandbox, so multiple people and multiple chats can run tests at the same time without interfering.
|
|
115
|
+
|
|
116
|
+
## What you get
|
|
117
|
+
|
|
118
|
+
The hosted server exposes the full live tool set:
|
|
119
|
+
|
|
120
|
+
| Tool | Purpose |
|
|
121
|
+
| --- | --- |
|
|
122
|
+
| `session_start`, `session_status`, `session_extend` | Start a sandbox, check its health, add more time |
|
|
123
|
+
| `find`, `findall`, `find_and_click` | Locate elements by plain-English description |
|
|
124
|
+
| `click`, `hover`, `type`, `press_keys`, `scroll` | Perform actions |
|
|
125
|
+
| `assert`, `check` | Ask yes/no questions about the screen |
|
|
126
|
+
| `screenshot`, `exec`, `wait`, `focus_application` | Capture state, run commands, pause |
|
|
127
|
+
|
|
128
|
+
Every action also returns the SDK code for that step, so the agent can write a runnable [Vitest](https://vitest.dev) test as it goes.
|
|
129
|
+
|
|
130
|
+
## Local server for CI and automation
|
|
131
|
+
|
|
132
|
+
For headless automation, or when you would rather use an API key than a browser login, run the server as a local stdio process:
|
|
133
|
+
|
|
134
|
+
```bash
|
|
135
|
+
npx -p testdriverai testdriverai-mcp
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
It reads `TD_API_KEY` from the environment. Generate a key at [console.testdriver.ai/settings](https://console.testdriver.ai/settings).
|
|
139
|
+
|
|
140
|
+
```json
|
|
141
|
+
{
|
|
142
|
+
"mcpServers": {
|
|
143
|
+
"testdriver": {
|
|
144
|
+
"type": "stdio",
|
|
145
|
+
"command": "npx",
|
|
146
|
+
"args": ["-p", "testdriverai", "testdriverai-mcp"],
|
|
147
|
+
"env": { "TD_API_KEY": "${TD_API_KEY}" }
|
|
148
|
+
}
|
|
149
|
+
}
|
|
150
|
+
}
|
|
151
|
+
```
|
|
152
|
+
|
|
153
|
+
<Tip>
|
|
154
|
+
`npx testdriverai init` writes this config for you, plus the TestDriver agent, skills, an example test, and a GitHub Actions workflow. See [Setting up your workspace](/quickstart-manual).
|
|
155
|
+
</Tip>
|
|
156
|
+
|
|
157
|
+
## Troubleshooting
|
|
158
|
+
|
|
159
|
+
<AccordionGroup>
|
|
160
|
+
<Accordion title="The tools do not appear in my client">
|
|
161
|
+
Confirm the URL is exactly `https://mcp.testdriver.ai/mcp`, check that you used the correct top-level config key for your client, and restart the client. Most clients read their MCP config only at startup.
|
|
162
|
+
</Accordion>
|
|
163
|
+
|
|
164
|
+
<Accordion title="The browser login never completes">
|
|
165
|
+
Your client must support OAuth 2.1 with Dynamic Client Registration. Older clients, and clients that only support stdio servers, cannot connect to the hosted URL. Use the local server with `TD_API_KEY` instead.
|
|
166
|
+
</Accordion>
|
|
167
|
+
|
|
168
|
+
<Accordion title="I ran out of device minutes">
|
|
169
|
+
Sandbox time is billed per minute. Check your usage and plan at [console.testdriver.ai](https://console.testdriver.ai).
|
|
170
|
+
</Accordion>
|
|
171
|
+
|
|
172
|
+
<Accordion title="The sandbox expired mid-session">
|
|
173
|
+
Sessions time out after a period of inactivity. Ask the agent to call `session_extend` before it expires, or `session_start` to get a fresh sandbox.
|
|
174
|
+
</Accordion>
|
|
175
|
+
</AccordionGroup>
|
|
176
|
+
|
|
177
|
+
## Next steps
|
|
178
|
+
|
|
179
|
+
<CardGroup cols={2}>
|
|
180
|
+
<Card title="Generating tests" icon="wand-magic-sparkles" href="/generating-tests" arrow horizontal>
|
|
181
|
+
Prompting patterns that get the best tests out of the agent.
|
|
182
|
+
</Card>
|
|
183
|
+
<Card title="Setting up your workspace" icon="wrench" href="/quickstart-manual" arrow horizontal>
|
|
184
|
+
Add the SDK to a project so generated tests run locally and in CI.
|
|
185
|
+
</Card>
|
|
186
|
+
<Card title="Walkthrough" icon="map" href="/provision" arrow horizontal>
|
|
187
|
+
Provision apps, locate elements, perform actions, and make assertions.
|
|
188
|
+
</Card>
|
|
189
|
+
<Card title="CI/CD" icon="circle-play" href="/ci-cd" arrow horizontal>
|
|
190
|
+
Run your tests on every pull request.
|
|
191
|
+
</Card>
|
|
192
|
+
</CardGroup>
|
|
@@ -8,7 +8,7 @@ icon: "wrench"
|
|
|
8
8
|
Add TestDriver to an existing project without the `init` scaffold. This is useful when you already have a Vitest setup or want full control over each file.
|
|
9
9
|
|
|
10
10
|
<Tip>
|
|
11
|
-
If you
|
|
11
|
+
If you only want to drive TestDriver from chat, [MCP Setup](/mcp-setup) is a single URL with nothing to install.
|
|
12
12
|
</Tip>
|
|
13
13
|
|
|
14
14
|
<Steps>
|
|
@@ -121,7 +121,7 @@ If you want to write tests with an AI assistant, connect the TestDriver agent an
|
|
|
121
121
|
npx testdriverai init --client cursor,claude-code,vscode --no-sample-test
|
|
122
122
|
```
|
|
123
123
|
|
|
124
|
-
See [
|
|
124
|
+
See [MCP Setup](/mcp-setup) for the configuration of each client.
|
|
125
125
|
|
|
126
126
|
## Next steps
|
|
127
127
|
|
package/docs/quickstart.mdx
CHANGED
|
@@ -11,8 +11,8 @@ TestDriver writes and runs computer-use tests for web apps, desktop apps, and br
|
|
|
11
11
|
<Card title="Add to GitHub" icon="github" href="/quickstart-github" arrow horizontal>
|
|
12
12
|
No install. Mention `@testdriverai` in a PR or issue and it writes, runs, and commits tests for you.
|
|
13
13
|
</Card>
|
|
14
|
-
<Card title="
|
|
15
|
-
|
|
14
|
+
<Card title="MCP Setup" icon="plug" href="/mcp-setup" arrow horizontal>
|
|
15
|
+
Add one URL to Claude, Cursor, VS Code, ChatGPT, or any MCP client. No install, no API key.
|
|
16
16
|
</Card>
|
|
17
17
|
<Card title="Manual" icon="wrench" href="/quickstart-manual" arrow horizontal>
|
|
18
18
|
Add TestDriver to an existing Vitest project file by file.
|