mcpbeat

Testdriver:hosted

testdriverai/testdriver:hosted

The fastest way to get started with TestDriver. Just set your API key and start testing.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
237
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/testdriverai/testdriverai --skill testdriver:hosted

The instruction itself

5 sections, as written by the author

<!-- Generated from hosted.mdx. DO NOT EDIT. -->

Hosted pricing is based on device-seconds: the amount of time your tests run on our infrastructure.

  • Zero Setup — Start testing immediately. No DevOps required.
  • Free Tier — Get started with a limited preview at no cost.
  • Pay As You Go — Only pay for the device-seconds you use.

Hosted Plans

<CardGroup cols={3}>

<Card title="Free Trial" icon="gift" href="https://docs.testdriver.ai">

$0/month

  • 1 Concurrent Sandbox
  • 60 Minutes Included
  • 1 Team User
  • Community Support

</Card>

<Card title="Pro" icon="rocket" href="https://console.testdriver.ai/checkout/pro">

$20/month per user

  • 2 Concurrent Sandboxes
  • 600 Minutes Included
  • Overage: $0.001/second
  • Test Recordings
  • Community Support

</Card>

<Card title="Team" icon="users" href="https://console.testdriver.ai/checkout/team">

$600/month

  • 8 Concurrent Sandboxes
  • 10,000 Minutes Included
  • Overage: $0.001/second
  • 5 Team Users
  • Test Recordings
  • Private Support
  • Test Analytics
  • CPU, RAM, & Network Profiles

</Card>

</CardGroup>

Get Started

Hosted is the default when you follow the Quickstart guide.

<Card

title="Try the Quickstart"

icon="play"

href="/v7/quickstart"

>

Set your API key and start testing in minutes.

</Card>

Parallel Testing Limits

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.

<Info>

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.

</Info>

Avoiding Slot Conflicts

To prevent tests from failing due to exceeding your license slot limit, we recommend two key configurations:

<AccordionGroup>

<Accordion title="Set Maximum Concurrency in Vitest">

Limit concurrent tests to match your available license slots:

    import { defineConfig } from 'vitest/config';
    import TestDriver from 'testdriverai/vitest';

    export default defineConfig({
      test: {
        testTimeout: 900000,
        hookTimeout: 900000,
        maxConcurrency: 5, // Set to your license slot limit
        reporters: ['default', TestDriver()],
        setupFiles: ['testdriverai/vitest/setup'],
      },
    });

<Tip>

Check your slot count at console.testdriver.ai and set maxConcurrency to that number or lower.

</Tip>

</Accordion>

<Accordion title="Use GitHub Concurrency Keys">

Prevent multiple workflow runs from competing for the same slots by using GitHub's concurrency controls:

    name: Tests

    on:
      push:
        branches: [main]
      pull_request:

    # Prevent concurrent runs from competing for license slots
    concurrency:
      group: ${{ github.workflow }}-${{ github.ref }}
      cancel-in-progress: true

    jobs:
      test:
        runs-on: ubuntu-latest
        steps:
          - uses: actions/checkout@v4
          
          - name: Setup Node.js
            uses: actions/setup-node@v4
            with:
              node-version: '20'
          
          - name: Install dependencies
            run: npm install
          
          - name: Run tests
            run: vitest run
            env:
              TD_API_KEY: ${{ secrets.TD_API_KEY }}

The concurrency block ensures:

  • Only one workflow run per branch runs at a time
  • New pushes cancel in-progress runs on the same branch
  • Different branches/PRs can run in parallel (up to your slot limit)

</Accordion>

</AccordionGroup>

When to Consider Self-Hosted

Hosted is perfect for getting started and for teams that want zero infrastructure management. However, you might consider Self-Hosted if you:

  • Want to escape per-second billing with a flat license fee
  • Require greater concurrency than offered in Cloud plans
  • Need full control over your infrastructure and privacy
  • Want to use your own AI API keys
  • Require custom hardware configurations
  • Have high test volumes that make self-hosting more economical

<Card

title="Explore Self-Hosted"

icon="server"

href="/v7/self-hosted"

>

Learn about self-hosting for unlimited test execution at a flat rate.

</Card>

How to use it

Copy the folder

Take testdriverai/testdriver:hosted from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm. Without those the skill loads but fails at the first command.