QA Team

Your AI-powered quality assurance team.

QA Team is a team of AI specialists that tests your application through intelligent exploration. Instead of writing brittle test code, it understands your app semantically and tests it like a human QA specialist would.

Price: $99 (one-time)

Quick Start

npx @aiorg/cli init qa-team ~/my-qa
cd ~/my-qa
claude
> /setup

Overview

You don't need to know testing syntax. QA Team explores and verifies — no brittle selectors, no flaky tests.

Traditional E2E TestsQA Team
Brittle selectors break when UI changesAI understands UI semantically
Tests verify happy pathsDestructive testing finds real bugs
You maintain test codeZero maintenance
Tests run in backgroundVisible browser — watch AI explore

Elite Tester Mindset

QA Team doesn't test to prove things work. It tests to find ALL the ways to break things.

  • How can I BREAK this?
  • What happens if I do things in the WRONG ORDER?
  • What if I click 10 times before the page loads?
  • What's the weirdest thing I can input?
  • What would an ANGRY user do?

Destructive Tours

TourWhat It Does
AntisocialSQL injection, XSS, IDOR, access /admin
InterruptionRefresh during submit, back button, double-click
ChaosSlow network, race conditions, concurrent tabs
Speed DemonEverything very fast, don't wait for loading
Edge Bomber10,000 chars, unicode, null bytes, negative IDs

What's Included

UI Testing (Browser)

CommandDescription
/setupConnect to target project, configure Playwright
/exploreExplore app structure and discover flows
/runExecute tests in target project
/flowsView and manage discovered flows
/evidenceView screenshots, logs, bug reports

API Testing (Backend)

CommandDescription
/api-discoverScan codebase, find all API endpoints
/api-exploreTest all discovered endpoints
/api-test [endpoint]Deep-test specific endpoint (30+ scenarios)
/api-generateGenerate stable test files

Test Generation (Paid)

CommandDescription
/planGenerate test plan from app structure
/generateGenerate Playwright tests and create PR
/healAnalyze and fix broken tests
/coverageAnalyze test coverage by flow

The Team

QA Team has two specialists:

UI Tester

Discovers your app by navigating pages, clicking buttons, filling forms. Uses Playwright MCP for browser control. Visible by default — you watch AI explore in a real browser.

API Tester

Tests your backend directly without a browser. Auto-discovers endpoints from code, tests auth/validation/security. Generates stable tests that don't depend on specific data.

Workflow

UI Testing

/setup → /explore → /run (repeat) → /generate (optional)
  1. Setup — Connect to target project
  2. Explore — AI discovers app structure (visible browser!)
  3. Run — AI re-executes flows, catches regressions
  4. Generate — (optional) Create Playwright tests for stable flows

API Testing

/setup → /api-discover → /api-explore → /api-generate (optional)
  1. Discover — Find all API endpoints in codebase
  2. Explore — Test each endpoint (auth, validation, security)
  3. Deep-test — Focus on specific endpoints
  4. Generate — Create stable test files

Evidence Collection

QA Team collects evidence like a professional tester:

EvidenceWhen Captured
ScreenshotsOn errors, key pages, form submissions
Console logsContinuously during exploration
Server logsWhen dev server runs
Network HARAll HTTP requests/responses
Bug reportsWhen issues are found

Bug Reports Include

  • Screenshot
  • Console errors with stack trace
  • Server logs
  • Steps to reproduce
  • Environment info

Security Testing

API Tester automatically checks for:

  • Auth bypass (accessing protected endpoints without token)
  • SQL injection
  • Missing validation (empty, null, too long inputs)
  • Information disclosure in errors
  • Missing rate limiting

Avoiding Flaky Tests

API Tester generates tests that don't depend on specific data:

// FLAKY (traditional)
expect(response.users.length).toBe(5);

// STABLE (QA Team)
expect(response.users).toBeInstanceOf(Array);

Related Kits

Works with any project:

FAQ

Q: Do I need to write tests?

No. QA Team explores your app and finds bugs without test code. Generated tests are optional for stable flows.

Q: Can I watch the AI test?

Yes! By default, QA Team opens a visible browser window. Use --headless for background execution.

Q: How is this different from Playwright tests?

Traditional tests verify happy paths with brittle selectors. QA Team thinks like an elite destructive tester — actively trying to break your app.

Q: Does this work with any project?

Yes. QA Team is a companion kit — works with any web application. Point it at localhost or staging URL.