Skip to content

DEVELOPMENT.md

Latest commit

 

History

History
53 lines (36 loc) · 1.83 KB

DEVELOPMENT.md

File metadata and controls

53 lines (36 loc) · 1.83 KB
Raw

Development Setup

This guide explains how to test changes from a branch without publishing to the marketplace.

Prerequisites

Install from a branch

Remove any existing installation, then add the marketplace pointing to your branch:

/plugin uninstall autonoma-test-planner-development
/plugin marketplace remove autonoma
/plugin marketplace add https://github.com/Autonoma-AI/test-planner-plugin#your-branch-name
/plugin install autonoma-test-planner-development@autonoma

Updating after changes

Push new commits to your branch, then reinstall:

/plugin uninstall autonoma-test-planner-development
/plugin marketplace remove autonoma
/plugin marketplace add https://github.com/Autonoma-AI/test-planner-plugin#your-branch-name
/plugin install autonoma-test-planner-development@autonoma

Environment variables

The plugin itself requires these values in the target project session:

Variable Description
AUTONOMA_API_KEY Autonoma API key
AUTONOMA_PROJECT_ID Application ID from the Autonoma dashboard
AUTONOMA_API_URL API base URL, for example http://localhost:4000 in local dev

You do not need to pre-set AUTONOMA_SDK_ENDPOINT, AUTONOMA_SHARED_SECRET, or AUTONOMA_SIGNING_SECRET. Step 1 creates or discovers those values in the target repo by editing .env and .env.example.

Use AUTONOMA_AUTO_ADVANCE=true as the canonical launch mode while testing. If you are still using the older confirmation flag, AUTONOMA_REQUIRE_CONFIRMATION=false is treated as the same auto-advance behavior.

After the generated PR is merged, the user still needs to deploy those env changes.

References