minitest-cli 0.16.0

Minitest CLI – command-line interface for the Minitest testing platform

minitest-cli

Command-line interface for the Minitest testing platform.

Installation

One-liner (recommended)

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/minitap-ai/minitest-cli/main/install.sh | bash

Windows (PowerShell):

powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/minitap-ai/minitest-cli/main/install.ps1 | iex"

Both scripts use uv if available, or install it automatically.

Other methods

uv (all platforms):

uv tool install minitest-cli

Homebrew (macOS):

brew install minitap-ai/tap/minitest-cli

uvx (zero-install, all platforms):

uvx --from minitest-cli minitest --help

From source:

git clone https://github.com/minitap-ai/minitest-cli.git
cd minitest-cli
uv sync
uv run minitest --help

Quick Start

# Authenticate
minitest auth login

# List your apps
minitest apps list

# Create a new app on your tenant
minitest apps create --name "My App"

# Run tests
minitest run --app <app-id>

Configuration

Environment Variable	Description	Required
MINITEST_TOKEN	API authentication token	Yes (or use minitest auth login)
MINITEST_APP_ID	Default app ID	No (can use --app flag)
MINITEST_API_URL	testing-service base URL	No (defaults to production)
MINITEST_APPS_MANAGER_URL	apps-manager base URL (used by minitest apps create)	No (defaults to production)
MINITEST_INTEGRATIONS_URL	minihands-integrations base URL (used to list tenants)	No (defaults to production)
MINITEST_SUPABASE_URL	Supabase project URL used for OAuth login	No (defaults to production)
MINITEST_SUPABASE_PUBLISHABLE_KEY	Supabase publishable (anon) key used for OAuth login	No (defaults to production)

The recommended way to set these is to copy .env.example to .env — the CLI loads .env automatically. The shipped .env.example already targets the dev environment (see below).

Global Flags

Flag	Description
--json	Output JSON to stdout (diagnostics go to stderr)
--app <id-or-name>	Target app for commands that require one
--version	Show CLI version
--help	Show help

Commands

Command	Description
minitest auth	Authentication management
minitest apps	App management
minitest user-story	User-story operations
minitest build	Build management
minitest run	Test execution

Exit Codes

Code	Meaning
0	Success
1	General error
2	Authentication error
3	Network / API error
4	Resource not found

Using the Dev Environment

The shipped .env.example already targets the dev environment, so pointing the CLI at dev is just a matter of loading it. Copy it to .env once:

cp .env.example .env

The CLI loads .env automatically, so every command now runs against dev — no per-command environment variables needed:

minitest auth login      # authenticates against dev, stores a dev-specific token
minitest apps list       # runs against dev

To target production instead, either omit the .env file (the built-in defaults point at production) or comment out the dev values and uncomment the # Production lines in your .env.

Tip: You can still override any single variable inline for a one-off command, e.g. MINITEST_API_URL=https://testing-service.dev.minitap.ai minitest apps list.

Development

# Install dependencies
uv sync --dev

# Run linter
uv run ruff check .

# Run formatter
uv run ruff format .

# Run type checker
uv run pyright

# Run tests
uv run pytest