Lazy Testing

AI-driven test automation for Claude Code. Zero setup. Zero test files. You're too lazy to write tests, so let the tool handle it.

What is this?

An MCP server that gives Claude the power to explore, understand, and test your web apps in a real browser. No config files, no page objects, no test scripts. You say "test my app" and it does the rest while you kick back.

Install

npm install -g lazytesting

Playwright's Chromium gets installed automatically. That's it. Go grab a coffee.

Hook it up to Claude Code

Add this to your Claude Code MCP config:

{
  "mcpServers": {
    "lazytesting": {
      "command": "lazytesting"
    }
  }
}

Or if you installed locally:

{
  "mcpServers": {
    "lazytesting": {
      "command": "node",
      "args": ["./node_modules/.bin/lazytesting"]
    }
  }
}

How it works

Talk to Claude. That's the whole workflow. Let the tool do the heavy lifting.

You:    "Test my app at localhost:3000"
Claude: explores the app, maps every page, detects auth, infers what kind of app it is
Claude: "I found a login page, a dashboard, and a settings panel.
         Got test credentials? Any areas I should focus on?"
You:    "[email protected] / password123. Focus on the dashboard."
Claude: runs real browser tests, screenshots every step, catches errors
Claude: "3 tests run. 2 passed. Delete button doesn't actually delete."

No test files were written. No test files were even thought about.

Tools

Four MCP tools. That's all you need.

| Tool | What it does | |------|-------------| | explore | Crawl an app. Map pages, forms, buttons, links. Detect auth. Take screenshots. | | test | Run tests from plain English or explicit steps. Real browser. Real screenshots. | | context | Teach it about your app. Credentials, focus areas, known issues. Persists across sessions. | | status | See what it knows. Pages mapped, test history, pass rates. |

Why Lazy Testing?

• Zero setup — No test files. No config. No page objects. Just a URL.
• Claude is the brain — The tool extracts everything, Claude does the thinking. You do nothing.
• Self-discovering — It explores your app and figures out what to test on its own.
• Persistent memory — Learns your app over time. Gets smarter every session.
• No port conflicts — Uses stdio, not HTTP. Stays completely out of your way.
• Real browser — Playwright under the hood. Real clicks on real elements. Not mock testing.

Requirements

• Node.js 18+
• Claude Code with MCP support

Data

Project data lives at ~/.lazytesting/projects/. Screenshots, app maps, test results — all there. Delete a project folder to forget about it.

License

MIT