testkit

testkit is a project scaffolding tool for modern test automation frameworks.

Supported projects today:

• Playwright
• Cypress
• WebdriverIO

Table of contents

• Feature matrix
• Use as npm CLI
• Use as MCP server
• Detailed documentation
• Contributing

Feature matrix

Feature	Playwright	Cypress	WebdriverIO
TypeScript template	✓	✓	✓
Built-in sample app for local testing	✓	✓	✓
API example	✓	✓	✓
Data factory	✓	✓	✓
Page objects / page modules	✓	✓	✓
Multi-environment support	✓	✓	✓
Secret management pattern	✓	✓	✓
Linting checks	✓	✓	✓
CI workflow	✓	✓	✓
Optional Allure report	✓	✓	✓
Docker support	✓	✓	✓
MCP scaffolding support	✓	✓	✓
AI-ready template guidance	✓	✓	✓
Safe template upgrade checks	✓	✓	✓

Use as npm CLI

Open the docs site for the live animated terminal walkthrough built with a Termynal-style interaction:

• Animated CLI walkthrough

# Run the scaffolder
npx @toolstackhq/create-testkit

# Launch the local setup UI wrapper
npx @toolstackhq/create-testkit --ui

? Select a template
? Target directory
? Run npm install now?
? Run npx playwright install now?   # Playwright only
? Run npm test now?

# Scaffold Playwright directly
npx @toolstackhq/create-testkit playwright-template my-project

# Scaffold Cypress directly
npx @toolstackhq/create-testkit cypress-template my-project

# Scaffold WebdriverIO directly
npx @toolstackhq/create-testkit wdio-template my-project

# Check for safe managed-template updates later
npx -y @toolstackhq/create-testkit upgrade check .

# Apply only safe managed-template updates
npx -y @toolstackhq/create-testkit upgrade apply --safe .

The local --ui flow is a browser wrapper over the same scaffold engine. It collects options visually, mirrors progress live, and still keeps the terminal as the primary execution surface.

Use as MCP server

Use the MCP server when you want an LLM to scaffold projects deterministically instead of generating framework boilerplate from scratch.

Generated templates also include:

• AI_CONTEXT.md for any LLM
• AGENTS.md as a thin pointer for tools that look for agent instructions

That means the generated project already carries framework-specific guidance for adding tests, updating page objects, and maintaining CI without the model inventing its own structure.

Codex

Add this to your Codex MCP config:

{
  "mcpServers": {
    "testkit": {
      "command": "npx",
      "args": ["-y", "@toolstackhq/testkit-mcp"]
    }
  }
}

Prompt example:

Create a Playwright framework in /tmp/pw-demo without installing dependencies.

Claude Code

Anthropic documents Claude Code MCP servers in a project .mcp.json file. Reference: Connect Claude Code to tools via MCP.

{
  "mcpServers": {
    "testkit": {
      "command": "npx",
      "args": ["-y", "@toolstackhq/testkit-mcp"]
    }
  }
}

Prompt example:

Describe the playwright-template and scaffold it in ./my-framework.

Detailed documentation

• Docs index
• MCP docs site
• Run locally
• Framework architecture
• Agent layer
• Write and extend tests
• Reporting
• CI and quality checks
• Security and secrets
• MCP server package
• Playwright template README
• Cypress template README
• WebdriverIO template README

Contributing

Open an issue or PR if you want to add:

• a new framework template
• shared upgrade logic
• new MCP tooling
• stronger CI or reporting patterns