mcpbeat Sign in

Testdriver:quickstart Agent Skill

Run your first computer-use test in minutes.

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:quickstart

The instruction itself

as written by the author

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

TestDriver makes it easy to write automated computer-use tests for web browsers, desktop apps, and more. Follow the directions below to run your first TestDriver test.

<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>

<Tabs>

<Tab title="CLI" icon="terminal">

Get started quickly with the TestDriver CLI.

<Steps>

<Step title="Install TestDriver">

Use npx to quickly set up an example project:

        npx testdriverai init

This will walk you through creating a new project folder, installing dependencies, setting up your API key, and configuring MCP for your preferred AI assistant (VS Code, Cursor, Claude Desktop, etc.).

</Step>

<Step title="Run Your Test">

TestDriver uses Vitest as the test runner. To run your test, use:

        vitest run

This will spawn a sandbox, launch Chrome, and run the example test!

</Step>

</Steps>

</Tab>

<Tab title="GitHub Copilot" icon="github">

Use the TestDriver VS Code extension with GitHub Copilot for an AI-powered testing workflow.

<Card

title="Install TestDriver for VS Code"

icon="/images/content/extension/vscode.svg"

href="vscode:extension/testdriver.testdriver"

arrow

horizontal

>

</Card>

The extension provides one-click sign-in, project initialization, a live preview panel for watching tests execute, and MCP server configuration for GitHub Copilot.

Once installed, follow the full setup guide to configure MCP and start building tests with AI assistance:

<Card

title="VS Code + Copilot Setup Guide"

icon="arrow-right"

href="/v7/copilot/setup"

arrow

horizontal

>

Sign in, initialize your project, and configure MCP for GitHub Copilot.

</Card>

</Tab>

<Tab title="Manual" icon="wrench">

Install TestDriver and manually create the files yourself.

<Steps>

<Step title="Create a TestDriver Account">

You will need a TestDriver account to get an API key.

<Card

title="Get an API Key"

icon="user-plus"

href="https://console.testdriver.ai/team"

arrow

horizontal

>

Start with 60 free device minutes, no credit-card required!

</Card>

</Step>

<Step title="Install Dependencies">

Install Vitest and TestDriver as dev dependencies:

        npm install --save-dev vitest testdriverai

</Step>

<Step title="Create a vitest.config.js File">

In your project root, create a vitest.config.js file with the following content:

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

        export default defineConfig({
          test: {
            testTimeout: 900000,
            hookTimeout: 900000,
            reporters: [
              'default',
              TestDriver()
            ],
            setupFiles: ['testdriverai/vitest/setup'],
          },
        });

</Step>

<Step title="Create an Example Test File">

Add your API key to the example test file below and save it as test.mjs in your project root.

        import { describe, expect, it } from "vitest";
        // Import TestDriver from the vitest hooks
        import { TestDriver } from "testdriverai/vitest/hooks";

        describe("Google Search Example", () => {
          it("should search for TestDriver", async (context) => {
            // Create TestDriver instance - automatically connects to sandbox
            const testdriver = TestDriver(context, {
              apiKey: 'YOUR_API_KEY_HERE' // supply your API key here 
            });

            // Provision Chrome browser with a URL
            // This also starts dashcam recording automatically
            await testdriver.provision.chrome({ url: "https://duckduckgo.com" });

            // Find and interact with elements using natural language
            const searchBox = await testdriver.find("DuckDuckGo search input field");
            await searchBox.click();

            // Type into the focused element
            await testdriver.type("testdriver.ai");

            // Press Enter to search
            await testdriver.pressKeys(["enter"]);

            // Assert something is visible on the page
            const result = await testdriver.assert("search results are displayed");
            expect(result).toBeTruthy();
          });
        });

</Step>

<Step title="Run Your Test">

TestDriver uses Vitest as the test runner. To run your test, use:

        vitest run

This will spawn a sandbox, launch Chrome, and run the example test!

</Step>

</Steps>

</Tab>

</Tabs>

Other skills for the same job

different authors, same section of the catalogue
Webapp Testing
by anthropics
vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Systematic Debugging
by ratacat
×7

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

10k tokens scripts
Verification Before Completion
by ZhanlinCui
×6

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

1k tokens
Backtest Expert
by BaggaT236
×3

Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.

15k tokens scripts
Adaptyv
by christophacham
×3

Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.

16k tokens
Aeon
by christophacham
×3

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.

19k tokens

How to use it

Copy the folder

Take testdriverai/testdriverai-testdriver:quickstart 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, npx. Without those the skill loads but fails at the first command.