autonoma-test-planner

Autonoma Test Planner

A Claude Code plugin that generates comprehensive E2E test suites for your codebase through a validated 6-step pipeline.

Each step runs in an isolated subagent with deterministic validation. The pipeline audits how application entities are created, implements an Autonoma Environment Factory against the target app, validates scenario lifecycles through the live endpoint, and only then generates E2E tests.

Install

/plugin marketplace add Autonoma-AI/test-planner-plugin
/plugin install autonoma-test-planner@autonoma

Usage

Inside any project with Claude Code:

/autonoma-test-planner:generate-tests

The full pipeline is interactive. After steps 1-5, Claude presents the step summary and waits for your confirmation before continuing.

Lifecycle reporting is hook-driven:

• hooks/pipeline-kickoff.sh creates the setup record and writes autonoma/.docs-url plus autonoma/.generation-id.
• hooks/validate-pipeline-output.sh validates artifacts, emits step events, uploads artifacts, and enforces the test-generation gate.
• hooks/pretool-heartbeat.sh keeps dashboard activity reporting alive while tools are running.

Pipeline

Step 1: Knowledge Base

Analyzes the app and produces autonoma/AUTONOMA.md, autonoma/skills/*.md, and autonoma/features.json.

You review: the core flows table.

Step 2: Entity Creation Audit

Audits every database model and records how each model comes into existence in autonoma/entity-audit.md.

Models marked independently_created: true become Environment Factory factories that call the app's real creation functions. Dependent-only models use the SDK's raw SQL fallback and are torn down through their owner model.

You review: factory-backed models, dependent-only models, and any dual-creation models.

Step 3: Scenarios

Reads the knowledge base and autonoma/entity-audit.md, then produces autonoma/scenarios.md.

Scenarios include standard, empty, and large, track variable fields that must vary across runs, and use nested create trees rooted at the scope entity.

You review: entity names, counts, relationships, variable fields, and via-owner versus standalone creation choices.

Step 4: Implement Environment Factory

Installs and configures the Autonoma SDK endpoint, then registers a factory for every independently_created: true model from entity-audit.md.

This step runs a signed discover smoke test and factory-integrity checks, then writes autonoma/.endpoint-implemented. It does not run full up / down; lifecycle validation happens in Step 5.

You review: handler path, installed packages, factories registered, and required secrets.

Step 5: Validate Scenario Lifecycle

Runs signed discover / up / down against every scenario. The validator may fix handler bugs or reconcile autonoma/scenarios.md with real endpoint behavior.

On success, it writes autonoma/scenario-recipes.json, autonoma/.scenario-validation.json, and autonoma/.endpoint-validated. The .endpoint-validated sentinel gates Step 6; test files cannot be written before it exists.

You review: scenarios passed, scenario edits, preflight result, and recipe upload status.

Step 6: Generate E2E Tests

Generates markdown test files in autonoma/qa-tests/ plus autonoma/qa-tests/INDEX.md.

You review: test distribution and coverage correlation.

Key Outputs

• autonoma/AUTONOMA.md
• autonoma/skills/*.md
• autonoma/features.json
• autonoma/entity-audit.md
• autonoma/scenarios.md
• autonoma/.factory-plan.md
• autonoma/.endpoint-implemented
• autonoma/scenario-recipes.json
• autonoma/.scenario-validation.json
• autonoma/.endpoint-validated
• autonoma/qa-tests/INDEX.md

Ad Hoc Test Generation

The same plugin includes a generate-adhoc-tests command that generates tests focused on a specific topic without regenerating your full test suite.

Usage

Pass your focus description directly after the command:

/autonoma-test-planner:generate-adhoc-tests description

Or invoke without arguments and the command will suggest focus areas based on your codebase:

/autonoma-test-planner:generate-adhoc-tests

How it works

Subsequent runs (active scenarios and recipes already exist in Autonoma): fetches existing scenario, skill, and test context from Autonoma, then runs only focused test generation for the requested topic.

Tests are written to autonoma/qa-tests/{focus-slug}/ so they sit alongside your existing test suite without overwriting it.

Running multiple focus areas

Each focus area run writes to its own subfolder and tracks its own generation ID file. Multiple topics can run in parallel:

autonoma/qa-tests/
├── canvas-interactions/      ← autonoma/.generation-id-canvas-interactions
└── signatures-and-documents/ ← autonoma/.generation-id-signatures-and-documents

Environment Variables