@testdriverai/agent 7.8.0-test.74 → 7.9.0-canary.1
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/agent/lib/sandbox.js +156 -0
- package/agent/lib/sdk.js +4 -4
- package/ai/skills/testdriver-enterprise/SKILL.md +2 -109
- package/ai/skills/testdriver-hosted/SKILL.md +156 -0
- package/ai/skills/testdriver-mcp/SKILL.md +2 -2
- package/ai/skills/testdriver-quickstart/SKILL.md +30 -2
- package/ai/skills/testdriver-self-hosted/SKILL.md +125 -43
- package/ai/skills/testdriver-test-results-json/SKILL.md +257 -0
- package/docs/_data/examples-manifest.json +46 -46
- package/docs/_scripts/generate-examples.js +127 -60
- package/docs/docs.json +27 -28
- package/docs/v7/examples/ai.mdx +4 -3
- package/docs/v7/examples/assert.mdx +19 -4
- package/docs/v7/examples/chrome-extension.mdx +36 -29
- package/docs/v7/examples/element-not-found.mdx +2 -1
- package/docs/v7/examples/exec-output.mdx +3 -4
- package/docs/v7/examples/exec-pwsh.mdx +3 -4
- package/docs/v7/examples/findall-coffee-icons.mdx +88 -0
- package/docs/v7/examples/focus-window.mdx +3 -4
- package/docs/v7/examples/hover-image.mdx +4 -3
- package/docs/v7/examples/hover-text-with-description.mdx +104 -0
- package/docs/v7/examples/hover-text.mdx +4 -3
- package/docs/v7/examples/installer.mdx +5 -4
- package/docs/v7/examples/launch-vscode-linux.mdx +3 -7
- package/docs/v7/examples/match-image.mdx +3 -2
- package/docs/v7/examples/parse.mdx +66 -0
- package/docs/v7/examples/press-keys.mdx +8 -14
- package/docs/v7/examples/scroll-keyboard.mdx +4 -3
- package/docs/v7/examples/scroll-until-image.mdx +3 -2
- package/docs/v7/examples/scroll.mdx +6 -14
- package/docs/v7/examples/type.mdx +1 -5
- package/docs/v7/examples/windows-installer.mdx +10 -4
- package/interfaces/vitest-plugin.mjs +2 -2
- package/package.json +2 -2
- package/setup/aws/install-dev-runner.sh +7 -2
- package/setup/aws/spawn-runner.sh +12 -0
package/agent/lib/sandbox.js
CHANGED
|
@@ -536,6 +536,162 @@ const createSandbox = function (emitter, analytics, sessionInstance) {
|
|
|
536
536
|
}
|
|
537
537
|
}
|
|
538
538
|
|
|
539
|
+
// ─── Handle pending slot claim (trigger.dev waitpoint flow) ────
|
|
540
|
+
// The API returned early with status: 'pending'. The SDK has now
|
|
541
|
+
// connected to Ably and entered presence (done in _initAbly above).
|
|
542
|
+
// Wait for the claim-slot task to publish slot-approved or slot-denied
|
|
543
|
+
// on the control channel, then re-call authenticate with slotApproved.
|
|
544
|
+
// On slot-denied, we poll forever (re-calling authenticate every 10s)
|
|
545
|
+
// until a slot opens, matching _httpPostWithConcurrencyRetry behavior.
|
|
546
|
+
var concurrencyRetryInterval = 10000;
|
|
547
|
+
var slotPollStart = Date.now();
|
|
548
|
+
while (reply.status === 'pending') {
|
|
549
|
+
logger.log('Slot claim pending — waiting for approval via Ably...');
|
|
550
|
+
|
|
551
|
+
var self = this;
|
|
552
|
+
var slotResolved = false;
|
|
553
|
+
var slotResolve, slotReject;
|
|
554
|
+
var slotDecisionPromise = new Promise(function (resolve, reject) {
|
|
555
|
+
slotResolve = resolve;
|
|
556
|
+
slotReject = reject;
|
|
557
|
+
});
|
|
558
|
+
|
|
559
|
+
var slotTimeout = setTimeout(function () {
|
|
560
|
+
if (slotResolved) return;
|
|
561
|
+
slotResolved = true;
|
|
562
|
+
try { self._sessionChannel.unsubscribe('control', onSlotControl); } catch (_) {}
|
|
563
|
+
slotReject(new Error('Slot claim timed out waiting for approval'));
|
|
564
|
+
}, 60000); // 60s timeout
|
|
565
|
+
if (slotTimeout.unref) slotTimeout.unref();
|
|
566
|
+
|
|
567
|
+
function onSlotControl(msg) {
|
|
568
|
+
var data = msg.data;
|
|
569
|
+
if (!data) return;
|
|
570
|
+
if (data.type === 'slot-approved') {
|
|
571
|
+
if (slotResolved) return;
|
|
572
|
+
slotResolved = true;
|
|
573
|
+
clearTimeout(slotTimeout);
|
|
574
|
+
try { self._sessionChannel.unsubscribe('control', onSlotControl); } catch (_) {}
|
|
575
|
+
slotResolve({ approved: true, data: data });
|
|
576
|
+
} else if (data.type === 'slot-denied') {
|
|
577
|
+
if (slotResolved) return;
|
|
578
|
+
slotResolved = true;
|
|
579
|
+
clearTimeout(slotTimeout);
|
|
580
|
+
try { self._sessionChannel.unsubscribe('control', onSlotControl); } catch (_) {}
|
|
581
|
+
slotResolve({ approved: false, data: data });
|
|
582
|
+
}
|
|
583
|
+
}
|
|
584
|
+
|
|
585
|
+
// Subscribe FIRST, then check history to close the race window
|
|
586
|
+
// between presence enter (done in _initAbly) and this subscription.
|
|
587
|
+
// The claim-slot task fires in response to presence enter, so the
|
|
588
|
+
// decision may already be published by the time we get here.
|
|
589
|
+
var slotControlSub = await self._sessionChannel.subscribe('control', onSlotControl);
|
|
590
|
+
|
|
591
|
+
// Check for decisions published before this subscription was active
|
|
592
|
+
if (!slotResolved && slotControlSub) {
|
|
593
|
+
try {
|
|
594
|
+
var histPage = await slotControlSub.historyBeforeSubscribe({ limit: 10 });
|
|
595
|
+
while (histPage && !slotResolved) {
|
|
596
|
+
for (var hi = 0; hi < histPage.items.length; hi++) {
|
|
597
|
+
onSlotControl(histPage.items[hi]);
|
|
598
|
+
if (slotResolved) break;
|
|
599
|
+
}
|
|
600
|
+
histPage = (!slotResolved && histPage.hasNext()) ? await histPage.next() : null;
|
|
601
|
+
}
|
|
602
|
+
} catch (histErr) {
|
|
603
|
+
logger.warn('[slots] Failed to check history for slot decision: ' + (histErr.message || histErr));
|
|
604
|
+
}
|
|
605
|
+
}
|
|
606
|
+
|
|
607
|
+
var slotDecision = await slotDecisionPromise;
|
|
608
|
+
|
|
609
|
+
if (!slotDecision.approved) {
|
|
610
|
+
// Slot denied — disconnect Ably and re-try the full authenticate
|
|
611
|
+
// flow after a delay, polling forever until a slot opens.
|
|
612
|
+
var elapsed = Date.now() - slotPollStart;
|
|
613
|
+
logger.log(
|
|
614
|
+
'Slot denied: ' + (slotDecision.data.message || 'concurrency limit reached') +
|
|
615
|
+
' — waiting ' + (concurrencyRetryInterval / 1000) + 's before retrying' +
|
|
616
|
+
' (' + Math.round(elapsed / 1000) + 's elapsed)...'
|
|
617
|
+
);
|
|
618
|
+
logger.log('Upgrade for more slots → https://console.testdriver.ai/checkout/team');
|
|
619
|
+
try {
|
|
620
|
+
if (this._ably) this._ably.close();
|
|
621
|
+
this._ably = null;
|
|
622
|
+
this._sessionChannel = null;
|
|
623
|
+
} catch (_) {}
|
|
624
|
+
|
|
625
|
+
await new Promise(function (resolve) {
|
|
626
|
+
var t = setTimeout(resolve, concurrencyRetryInterval);
|
|
627
|
+
if (t.unref) t.unref();
|
|
628
|
+
});
|
|
629
|
+
|
|
630
|
+
// Re-call authenticate — this goes through _httpPostWithConcurrencyRetry
|
|
631
|
+
// so transient HTTP errors are also handled. The new reply will either
|
|
632
|
+
// be 'pending' again (loop continues) or succeed directly.
|
|
633
|
+
reply = await this._httpPostWithConcurrencyRetry(
|
|
634
|
+
"/api/v7/sandbox/authenticate",
|
|
635
|
+
body,
|
|
636
|
+
timeout,
|
|
637
|
+
);
|
|
638
|
+
|
|
639
|
+
if (!reply.success && reply.status !== 'pending') {
|
|
640
|
+
var retryErr = new Error(
|
|
641
|
+
reply.errorMessage || "Failed to allocate sandbox",
|
|
642
|
+
);
|
|
643
|
+
retryErr.responseData = reply;
|
|
644
|
+
throw retryErr;
|
|
645
|
+
}
|
|
646
|
+
|
|
647
|
+
// Re-init Ably if we got a new pending reply with fresh credentials
|
|
648
|
+
if (reply.status === 'pending' && reply.ably && reply.ably.token) {
|
|
649
|
+
this._sandboxId = reply.sandboxId;
|
|
650
|
+
this._teamId = reply.teamId;
|
|
651
|
+
await this._initAbly(reply.ably.token, reply.ably.channel);
|
|
652
|
+
this.instanceSocketConnected = true;
|
|
653
|
+
}
|
|
654
|
+
|
|
655
|
+
continue; // loop back to wait for the next slot decision
|
|
656
|
+
}
|
|
657
|
+
|
|
658
|
+
logger.log('Slot approved — provisioning sandbox...');
|
|
659
|
+
|
|
660
|
+
// Re-call authenticate with slotApproved flag to trigger provisioning
|
|
661
|
+
// Keep the same sandboxId so the Ably channel stays valid
|
|
662
|
+
var provisionBody = {
|
|
663
|
+
apiKey: this.apiKey,
|
|
664
|
+
version: version,
|
|
665
|
+
os: message.os || this.os || 'linux',
|
|
666
|
+
session: sessionId,
|
|
667
|
+
apiRoot: this.apiRoot,
|
|
668
|
+
sandboxId: this._sandboxId,
|
|
669
|
+
slotApproved: true,
|
|
670
|
+
};
|
|
671
|
+
if (message.resolution) provisionBody.resolution = message.resolution;
|
|
672
|
+
if (message.ci) provisionBody.ci = message.ci;
|
|
673
|
+
if (message.ami) provisionBody.ami = message.ami;
|
|
674
|
+
if (message.instanceType) provisionBody.instanceType = message.instanceType;
|
|
675
|
+
if (message.e2bTemplateId) provisionBody.e2bTemplateId = message.e2bTemplateId;
|
|
676
|
+
if (message.keepAlive !== undefined) provisionBody.keepAlive = message.keepAlive;
|
|
677
|
+
|
|
678
|
+
reply = await this._httpPostWithConcurrencyRetry(
|
|
679
|
+
"/api/v7/sandbox/authenticate",
|
|
680
|
+
provisionBody,
|
|
681
|
+
timeout,
|
|
682
|
+
);
|
|
683
|
+
|
|
684
|
+
if (!reply.success) {
|
|
685
|
+
var provisionErr = new Error(
|
|
686
|
+
reply.errorMessage || "Failed to provision sandbox after approval",
|
|
687
|
+
);
|
|
688
|
+
provisionErr.responseData = reply;
|
|
689
|
+
throw provisionErr;
|
|
690
|
+
}
|
|
691
|
+
|
|
692
|
+
break; // slot approved and provisioned — exit the while loop
|
|
693
|
+
}
|
|
694
|
+
|
|
539
695
|
if (message.type === "create") {
|
|
540
696
|
// E2B (Linux) sandboxes return a url directly.
|
|
541
697
|
// We still need to wait for runner.ready since sandbox-agent.js runs inside E2B.
|
package/agent/lib/sdk.js
CHANGED
|
@@ -273,9 +273,9 @@ const createSDK = (emitter, config, sessionInstance) => {
|
|
|
273
273
|
if (status >= 500) {
|
|
274
274
|
const serverError = new Error(
|
|
275
275
|
data?.message ||
|
|
276
|
-
`
|
|
276
|
+
`An error occurred on the TestDriver server (HTTP ${status}). Please try again later.`
|
|
277
277
|
);
|
|
278
|
-
serverError.code = data?.error || "
|
|
278
|
+
serverError.code = data?.error || "SERVER_ERROR";
|
|
279
279
|
serverError.isServerError = true;
|
|
280
280
|
serverError.originalError = error;
|
|
281
281
|
return serverError;
|
|
@@ -567,9 +567,9 @@ const createSDK = (emitter, config, sessionInstance) => {
|
|
|
567
567
|
if (status >= 500) {
|
|
568
568
|
const serverError = new Error(
|
|
569
569
|
error.response?.data?.message ||
|
|
570
|
-
`
|
|
570
|
+
`An error occurred on the TestDriver server (HTTP ${status}). Please try again later.`
|
|
571
571
|
);
|
|
572
|
-
serverError.code = error.response?.data?.error || "
|
|
572
|
+
serverError.code = error.response?.data?.error || "SERVER_ERROR";
|
|
573
573
|
serverError.isServerError = true;
|
|
574
574
|
serverError.originalError = error;
|
|
575
575
|
serverError.path = path;
|
|
@@ -1,114 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: testdriver:enterprise
|
|
3
|
-
description:
|
|
3
|
+
description: Self-hosted enterprise deployments with assisted setup and dedicated support
|
|
4
4
|
---
|
|
5
5
|
<!-- Generated from enterprise.mdx. DO NOT EDIT. -->
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
<CardGroup cols={2}>
|
|
10
|
-
<Card title="Air-Gapped Security" icon="shield-check">
|
|
11
|
-
Deploy everything in your environment. No data leaves your network. Complete isolation from external services.
|
|
12
|
-
</Card>
|
|
13
|
-
<Card title="Full Customization" icon="gear">
|
|
14
|
-
Custom integrations, dedicated infrastructure, and tailored solutions for your unique requirements.
|
|
15
|
-
</Card>
|
|
16
|
-
<Card title="Self-Hosted Dashboard & API" icon="server">
|
|
17
|
-
Run the entire TestDriver stack — dashboard, API, and test infrastructure — within your own environment.
|
|
18
|
-
</Card>
|
|
19
|
-
<Card title="Dedicated Support" icon="headset">
|
|
20
|
-
Direct access to our engineering team for implementation, customization, and ongoing support.
|
|
21
|
-
</Card>
|
|
22
|
-
</CardGroup>
|
|
23
|
-
|
|
24
|
-
## Who Needs Enterprise?
|
|
25
|
-
|
|
26
|
-
Enterprise is designed for organizations that:
|
|
27
|
-
|
|
28
|
-
- **Require air-gapped deployments** — Regulated industries, government, defense, or strict compliance requirements
|
|
29
|
-
- **Cannot use external APIs** — Data must never leave your network perimeter
|
|
30
|
-
- **Need custom integrations** — Unique CI/CD systems, internal tools, or specialized workflows
|
|
31
|
-
- **Want dedicated support** — Direct engineering support for complex implementations
|
|
32
|
-
|
|
33
|
-
## What's Included
|
|
34
|
-
|
|
35
|
-
### Fully Self-Hosted Stack
|
|
36
|
-
|
|
37
|
-
Unlike [Self-Hosted](/v7/self-hosted) (which uses TestDriver's hosted dashboard and API), Enterprise deploys everything in your environment:
|
|
38
|
-
|
|
39
|
-
| Component | Self-Hosted | Enterprise |
|
|
40
|
-
|-----------|-------------|------------|
|
|
41
|
-
| Test Sandboxes | Your infrastructure | Your infrastructure |
|
|
42
|
-
| Dashboard | TestDriver hosted | Your infrastructure |
|
|
43
|
-
| API | TestDriver hosted | Your infrastructure |
|
|
44
|
-
| AI Processing | Your API keys | Your infrastructure |
|
|
45
|
-
| Data Storage | Your AWS account | Your infrastructure |
|
|
46
|
-
|
|
47
|
-
### Custom Contract Terms
|
|
48
|
-
|
|
49
|
-
- Volume-based pricing
|
|
50
|
-
- Custom SLAs
|
|
51
|
-
- Dedicated support channels
|
|
52
|
-
- Professional services for implementation
|
|
53
|
-
- Training for your team
|
|
54
|
-
|
|
55
|
-
## Implementation Process
|
|
56
|
-
|
|
57
|
-
<Steps>
|
|
58
|
-
<Step title="Discovery Call">
|
|
59
|
-
Discuss your requirements, security constraints, and integration needs with our team.
|
|
60
|
-
</Step>
|
|
61
|
-
|
|
62
|
-
<Step title="Architecture Review">
|
|
63
|
-
Our engineers design a deployment architecture that meets your security and compliance requirements.
|
|
64
|
-
</Step>
|
|
65
|
-
|
|
66
|
-
<Step title="Deployment">
|
|
67
|
-
We work with your team to deploy TestDriver within your environment, including dashboard, API, and test infrastructure.
|
|
68
|
-
</Step>
|
|
69
|
-
|
|
70
|
-
<Step title="Integration">
|
|
71
|
-
Connect TestDriver to your CI/CD pipelines, internal tools, and workflows.
|
|
72
|
-
</Step>
|
|
73
|
-
|
|
74
|
-
<Step title="Training & Handoff">
|
|
75
|
-
Comprehensive training for your team on operating and maintaining the deployment.
|
|
76
|
-
</Step>
|
|
77
|
-
</Steps>
|
|
78
|
-
|
|
79
|
-
## Security & Compliance
|
|
80
|
-
|
|
81
|
-
Enterprise deployments support:
|
|
82
|
-
|
|
83
|
-
- **SOC 2** compliance requirements
|
|
84
|
-
- **HIPAA** for healthcare applications
|
|
85
|
-
- **FedRAMP** for government deployments
|
|
86
|
-
- **PCI DSS** for payment processing
|
|
87
|
-
- **Custom compliance frameworks** as needed
|
|
88
|
-
|
|
89
|
-
<Note>
|
|
90
|
-
All data remains within your network perimeter. TestDriver has no access to your test results, application data, or infrastructure.
|
|
91
|
-
</Note>
|
|
92
|
-
|
|
93
|
-
## Comparison: Self-Hosted vs Enterprise
|
|
94
|
-
|
|
95
|
-
| Feature | Self-Hosted | Enterprise |
|
|
96
|
-
|---------|-------------|------------|
|
|
97
|
-
| **Test Infrastructure** | Your AWS | Your infrastructure (any) |
|
|
98
|
-
| **Dashboard** | TestDriver cloud | Your infrastructure |
|
|
99
|
-
| **API** | TestDriver cloud | Your infrastructure |
|
|
100
|
-
| **Data Location** | Your AWS + TestDriver | 100% your infrastructure |
|
|
101
|
-
| **Network Requirements** | Internet access | Can be fully air-gapped |
|
|
102
|
-
| **Cloud Providers** | AWS only | Any (AWS, Azure, GCP, on-prem) |
|
|
103
|
-
| **Support** | Standard | Dedicated engineering |
|
|
104
|
-
| **Contract** | Standard licensing | Custom terms |
|
|
105
|
-
|
|
106
|
-
## Get Started
|
|
107
|
-
|
|
108
|
-
<Card
|
|
109
|
-
title="Schedule a Consultation"
|
|
110
|
-
icon="calendar"
|
|
111
|
-
href="https://calendly.com/d/cq23-qyn-3v6/testdriver-ai-demo"
|
|
112
|
-
>
|
|
113
|
-
Discuss your requirements with our team and get a custom proposal for your Enterprise deployment.
|
|
114
|
-
</Card>
|
|
7
|
+
This page has moved to [Self-Hosted](/v7/self-hosted).
|
|
@@ -0,0 +1,156 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: testdriver:hosted
|
|
3
|
+
description: The fastest way to get started with TestDriver. Just set your API key and start testing.
|
|
4
|
+
---
|
|
5
|
+
<!-- Generated from hosted.mdx. DO NOT EDIT. -->
|
|
6
|
+
|
|
7
|
+
Hosted pricing is based on **device-seconds**: the amount of time your tests run on **our infrastructure**.
|
|
8
|
+
|
|
9
|
+
- **Zero Setup** — Start testing immediately. No DevOps required.
|
|
10
|
+
- **Free Tier** — Get started with a limited preview at no cost.
|
|
11
|
+
- **Pay As You Go** — Only pay for the device-seconds you use.
|
|
12
|
+
|
|
13
|
+
## Hosted Plans
|
|
14
|
+
|
|
15
|
+
<CardGroup cols={3}>
|
|
16
|
+
<Card title="Free Trial" icon="gift" href="https://docs.testdriver.ai">
|
|
17
|
+
**$0/month**
|
|
18
|
+
|
|
19
|
+
- 1 Concurrent Sandbox
|
|
20
|
+
- 60 Minutes Included
|
|
21
|
+
- 1 Team User
|
|
22
|
+
- Community Support
|
|
23
|
+
</Card>
|
|
24
|
+
|
|
25
|
+
<Card title="Pro" icon="rocket" href="https://console.testdriver.ai/checkout/pro">
|
|
26
|
+
**$20/month**
|
|
27
|
+
|
|
28
|
+
- 2 Concurrent Sandboxes
|
|
29
|
+
- 600 Minutes Included
|
|
30
|
+
- Overage: $0.002/second
|
|
31
|
+
- 1 Team User
|
|
32
|
+
- Test Recordings
|
|
33
|
+
- Community Support
|
|
34
|
+
</Card>
|
|
35
|
+
|
|
36
|
+
<Card title="Team" icon="users" href="https://console.testdriver.ai/checkout/team">
|
|
37
|
+
**$600/month**
|
|
38
|
+
|
|
39
|
+
- 8 Concurrent Sandboxes
|
|
40
|
+
- 10,000 Minutes Included
|
|
41
|
+
- Overage: $0.001/second
|
|
42
|
+
- 5 Team Users
|
|
43
|
+
- Test Recordings
|
|
44
|
+
- Private Support
|
|
45
|
+
- Test Analytics
|
|
46
|
+
- CPU, RAM, & Network Profiles
|
|
47
|
+
</Card>
|
|
48
|
+
</CardGroup>
|
|
49
|
+
|
|
50
|
+
## Get Started
|
|
51
|
+
Hosted is the default when you follow the Quickstart guide.
|
|
52
|
+
<Card
|
|
53
|
+
title="Try the Quickstart"
|
|
54
|
+
icon="play"
|
|
55
|
+
href="/v7/quickstart"
|
|
56
|
+
>
|
|
57
|
+
Set your API key and start testing in minutes.
|
|
58
|
+
</Card>
|
|
59
|
+
|
|
60
|
+
## Parallel Testing Limits
|
|
61
|
+
|
|
62
|
+
Your account has a set number of **license slots** that determine how many devices can run simultaneously. You can view your available slots in the [TestDriver Dashboard](https://console.testdriver.ai).
|
|
63
|
+
|
|
64
|
+
<Info>
|
|
65
|
+
**When is a slot in use?** A license slot is occupied when a test client is connected. As soon as your device is destroyed the slot becomes available immediately.
|
|
66
|
+
</Info>
|
|
67
|
+
|
|
68
|
+
## Avoiding Slot Conflicts
|
|
69
|
+
|
|
70
|
+
To prevent tests from failing due to exceeding your license slot limit, we recommend two key configurations:
|
|
71
|
+
|
|
72
|
+
<AccordionGroup>
|
|
73
|
+
<Accordion title="Set Maximum Concurrency in Vitest">
|
|
74
|
+
Limit concurrent tests to match your available license slots:
|
|
75
|
+
|
|
76
|
+
```javascript vitest.config.mjs
|
|
77
|
+
import { defineConfig } from 'vitest/config';
|
|
78
|
+
import { TestDriver } from 'testdriverai/vitest';
|
|
79
|
+
|
|
80
|
+
export default defineConfig({
|
|
81
|
+
test: {
|
|
82
|
+
testTimeout: 900000,
|
|
83
|
+
hookTimeout: 900000,
|
|
84
|
+
maxConcurrency: 5, // Set to your license slot limit
|
|
85
|
+
reporters: ['default', TestDriver()],
|
|
86
|
+
setupFiles: ['testdriverai/vitest/setup'],
|
|
87
|
+
},
|
|
88
|
+
});
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
<Tip>
|
|
92
|
+
Check your slot count at [console.testdriver.ai](https://console.testdriver.ai) and set `maxConcurrency` to that number or lower.
|
|
93
|
+
</Tip>
|
|
94
|
+
</Accordion>
|
|
95
|
+
|
|
96
|
+
<Accordion title="Use GitHub Concurrency Keys">
|
|
97
|
+
Prevent multiple workflow runs from competing for the same slots by using [GitHub's concurrency controls](https://docs.github.com/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs):
|
|
98
|
+
|
|
99
|
+
```yaml .github/workflows/test.yml
|
|
100
|
+
name: Tests
|
|
101
|
+
|
|
102
|
+
on:
|
|
103
|
+
push:
|
|
104
|
+
branches: [main]
|
|
105
|
+
pull_request:
|
|
106
|
+
|
|
107
|
+
# Prevent concurrent runs from competing for license slots
|
|
108
|
+
concurrency:
|
|
109
|
+
group: ${{ github.workflow }}-${{ github.ref }}
|
|
110
|
+
cancel-in-progress: true
|
|
111
|
+
|
|
112
|
+
jobs:
|
|
113
|
+
test:
|
|
114
|
+
runs-on: ubuntu-latest
|
|
115
|
+
steps:
|
|
116
|
+
- uses: actions/checkout@v4
|
|
117
|
+
|
|
118
|
+
- name: Setup Node.js
|
|
119
|
+
uses: actions/setup-node@v4
|
|
120
|
+
with:
|
|
121
|
+
node-version: '20'
|
|
122
|
+
|
|
123
|
+
- name: Install dependencies
|
|
124
|
+
run: npm install
|
|
125
|
+
|
|
126
|
+
- name: Run tests
|
|
127
|
+
run: vitest run
|
|
128
|
+
env:
|
|
129
|
+
TD_API_KEY: ${{ secrets.TD_API_KEY }}
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
The `concurrency` block ensures:
|
|
133
|
+
- Only one workflow run per branch runs at a time
|
|
134
|
+
- New pushes cancel in-progress runs on the same branch
|
|
135
|
+
- Different branches/PRs can run in parallel (up to your slot limit)
|
|
136
|
+
</Accordion>
|
|
137
|
+
</AccordionGroup>
|
|
138
|
+
|
|
139
|
+
## When to Consider Self-Hosted
|
|
140
|
+
|
|
141
|
+
Hosted is perfect for getting started and for teams that want zero infrastructure management. However, you might consider [Self-Hosted](/v7/self-hosted) if you:
|
|
142
|
+
|
|
143
|
+
- Want to escape per-second billing with a flat license fee
|
|
144
|
+
- Require greater concurrency than offered in Cloud plans
|
|
145
|
+
- Need full control over your infrastructure and privacy
|
|
146
|
+
- Want to use your own AI API keys
|
|
147
|
+
- Require custom hardware configurations
|
|
148
|
+
- Have high test volumes that make self-hosting more economical
|
|
149
|
+
|
|
150
|
+
<Card
|
|
151
|
+
title="Explore Self-Hosted"
|
|
152
|
+
icon="server"
|
|
153
|
+
href="/v7/self-hosted"
|
|
154
|
+
>
|
|
155
|
+
Learn about self-hosting for unlimited test execution at a flat rate.
|
|
156
|
+
</Card>
|
|
@@ -9,7 +9,7 @@ TestDriver makes it easy to write automated computer-use tests for web browsers,
|
|
|
9
9
|
<Tip><a href="https://discord.com/invite/cWDFW8DzPm" target="_blank" rel="noreferrer">Join our Discord</a> if you have any questions or need help getting started!</Tip>
|
|
10
10
|
|
|
11
11
|
<Tabs>
|
|
12
|
-
<Tab title="
|
|
12
|
+
<Tab title="CLI" icon="terminal">
|
|
13
13
|
|
|
14
14
|
Get started quickly with the TestDriver CLI.
|
|
15
15
|
|
|
@@ -39,7 +39,35 @@ TestDriver makes it easy to write automated computer-use tests for web browsers,
|
|
|
39
39
|
</Step>
|
|
40
40
|
</Steps>
|
|
41
41
|
</Tab>
|
|
42
|
-
<Tab title="
|
|
42
|
+
<Tab title="GitHub Copilot" icon="github">
|
|
43
|
+
|
|
44
|
+
Use the TestDriver VS Code extension with GitHub Copilot for an AI-powered testing workflow.
|
|
45
|
+
|
|
46
|
+
<Card
|
|
47
|
+
title="Install TestDriver for VS Code"
|
|
48
|
+
icon="/images/content/extension/vscode.svg"
|
|
49
|
+
href="vscode:extension/testdriver.testdriver"
|
|
50
|
+
arrow
|
|
51
|
+
horizontal
|
|
52
|
+
>
|
|
53
|
+
</Card>
|
|
54
|
+
|
|
55
|
+
The extension provides one-click sign-in, project initialization, a live preview panel for watching tests execute, and MCP server configuration for GitHub Copilot.
|
|
56
|
+
|
|
57
|
+
Once installed, follow the full setup guide to configure MCP and start building tests with AI assistance:
|
|
58
|
+
|
|
59
|
+
<Card
|
|
60
|
+
title="VS Code + Copilot Setup Guide"
|
|
61
|
+
icon="arrow-right"
|
|
62
|
+
href="/v7/copilot/setup"
|
|
63
|
+
arrow
|
|
64
|
+
horizontal
|
|
65
|
+
>
|
|
66
|
+
Sign in, initialize your project, and configure MCP for GitHub Copilot.
|
|
67
|
+
</Card>
|
|
68
|
+
|
|
69
|
+
</Tab>
|
|
70
|
+
<Tab title="Manual" icon="wrench">
|
|
43
71
|
|
|
44
72
|
Install TestDriver and manually create the files yourself.
|
|
45
73
|
|