Introduction

What is Oorty?

Oorty was built for developers who ship fast with AI tools like v0, Cursor, and Bolt. These tools make building apps incredibly fast, but testing often gets skipped because setup is tedious.

Oorty solves this by providing a single command that sets up your entire testing infrastructure:

• Unit tests with Vitest for utilities and hooks
• Component tests with Testing Library for React components
• E2E tests with Playwright for full user flows
• CI/CD with GitHub Actions for automated testing

Key Features

CLI commands

The published CLI exposes these commands (see each page for flags and examples):

• oorty init — scaffold config and tooling
• oorty doctor — validate the setup
• oorty add — add a single unit, component, or E2E test template
• oorty plan (Pro) — AI test plan
• oorty generate (Pro) — generate tests from the plan JSON
• oorty coverage (Free) — Vitest V8 coverage (terminal + summary; optional HTML)
• oorty clean — manage and clean up the .oorty directory

Generated Files

After running oorty init, your project will have these configuration files:

my-app/
├── .github/
│   └── workflows/
│       └── test.yml      # CI workflow
├── .oorty/               # Single source of truth
│   ├── cache/            # Ephemeral (gitignored)
│   ├── plans/            # Test plans (tracked)
│   ├── analysis/         # Coverage snapshots (gitignored)
│   └── logs/             # Debug logs (gitignored)
├── oorty.json            # Oorty configuration
├── vitest.config.ts      # Vitest configuration
└── playwright.config.ts  # Playwright configuration

The .oorty/ directory is the single source of truth for auto-generated files. Plans are tracked in git for CI/collaboration, while cache and analysis are gitignored and rebuilt locally.