E2E Test Planner

The Test Planner is a Claude Code plugin that takes a web application codebase and runs a five-step pipeline:

1. integrate the Autonoma SDK into your project
2. generate a knowledge base
3. design test data scenarios
4. generate E2E tests
5. validate the scenarios against the live endpoint

The final output is a test suite plus validated scenario recipes that Autonoma can execute against your Environment Factory endpoint.

Installation

/plugin marketplace add Autonoma-AI/test-planner-plugin

/plugin install autonoma-test-planner@autonoma

/autonoma-test-planner:generate-tests

Before you start

The plugin still runs primarily against your frontend codebase, but it now starts by wiring the SDK integration itself instead of expecting you to provide a ready-made endpoint up front.

Before you start, make sure you have:

• access to the frontend codebase
• access to the backend codebase if it lives separately from the frontend
• these environment variables in the Claude Code session:
  • AUTONOMA_API_KEY
  • AUTONOMA_PROJECT_ID
  • AUTONOMA_API_URL

Optional:

• AUTONOMA_AUTO_ADVANCE=true to keep the plugin moving automatically after Steps 1-4
• AUTONOMA_REQUIRE_CONFIRMATION=false as a temporary compatibility alias for older launcher flows

You do not need to pre-supply the SDK endpoint URL or the shared request-signing secret anymore. The plugin creates the branch, installs the SDK, starts a local dev server, verifies the endpoint, and writes the discovered endpoint URL into the pipeline artifacts.

If your stack is unsupported, the plugin stops in Step 1 and tells you how to contact Autonoma.

The five steps

Step 1 - SDK Integration

The plugin detects your stack, installs the SDK from the appropriate package manager, wires the endpoint into your app, starts a dev server, and verifies discover, up, and down.

Consumes: Your repo plus the synced plugin SDK matrix. Produces: working SDK integration + autonoma/.sdk-endpoint

Step 2 - Generate a knowledge base

The agent analyzes your codebase and produces AUTONOMA.md: a user-perspective guide to your pages, flows, and interactions. It also generates skills/ files the test runner can use for navigation.

Consumes: Your codebase. Produces: autonoma/AUTONOMA.md + autonoma/skills/*.md

Step 3 - Generate test data scenarios

The agent uses the SDK discover artifact captured during Step 1, plus the knowledge base, to design the standard, empty, and large scenarios.

Consumes: Knowledge base + verified SDK endpoint/discover output. Produces: autonoma/discover.json + autonoma/scenarios.md

Step 4 - Generate E2E tests

The agent generates an E2E test suite as natural-language markdown files organized by flow and priority.

Consumes: Knowledge base + scenarios. Produces: autonoma/qa-tests/INDEX.md + autonoma/qa-tests/**/*

Step 5 - Scenario Validation

The plugin validates the planned scenarios against the live endpoint from Step 1, smoke-tests the lifecycle, and uploads executable recipe artifacts.

Consumes: discover.json + scenarios.md + live SDK endpoint. Produces: autonoma/scenario-recipes.json

How the steps connect

• Step 1 makes the rest of the pipeline possible by producing a verified SDK endpoint.
• Step 2 gives the planner the user-facing map of the product.
• Step 3 turns the verified schema and product context into concrete scenario plans.
• Step 4 turns those plans into executable E2E test coverage.
• Step 5 turns the scenario plan into validated runtime recipes.

Validation model

The plugin uses deterministic validators, not LLM-only checks:

• PostToolUse hooks validate file writes immediately.
• Step-level validators verify required formats and cross-file consistency.
• Recipe preflight checks verify that generated scenarios work against the live endpoint.

If validation fails, the pipeline stops and the agent must fix the issue before continuing.

Review checkpoints

The canonical launch mode is AUTONOMA_AUTO_ADVANCE=true, which keeps the plugin moving after Steps 1-4. If you are still using the older confirmation flag, AUTONOMA_REQUIRE_CONFIRMATION=false behaves the same way. When a review checkpoint appears, focus on: