Skip to Content
CLI ReferenceOverview

CLI Overview

AgenticAssure provides a command-line interface for every stage of the testing workflow: scaffolding projects, validating scenario files, listing scenarios, and running tests with full reporting. All commands are accessible through the agenticassure entry point.

Commands at a Glance

CommandDescription
agenticassure run <path>Run test scenarios against an agent and generate reports
agenticassure validate <path>Validate YAML scenario files against the JSON Schema
agenticassure list <path>List all scenarios with their metadata
agenticassure init [directory]Scaffold a new project with example scenarios

Global Options

These options are available on the root agenticassure command, before any subcommand:

OptionDescription
--versionPrint the installed version of AgenticAssure and exit
--helpShow the top-level help message and exit
agenticassure --version # agenticassure, version 0.2.0-alpha agenticassure --help

Getting Help for Any Command

Every command supports the --help flag, which prints usage information, all available options, and their defaults.

agenticassure run --help agenticassure validate --help agenticassure list --help agenticassure init --help

Typical Workflow

A typical workflow using the CLI follows this sequence:

  1. Scaffold a project with agenticassure init to create the directory structure and example scenarios.
  2. Edit scenarios in the generated scenarios/ directory, adding your own test cases.
  3. Validate your files with agenticassure validate scenarios/ to catch schema errors before running.
  4. List scenarios with agenticassure list scenarios/ to confirm everything loaded correctly.
  5. Run tests with agenticassure run scenarios/ --adapter mymodule.MyAgent to execute scenarios against your agent.
  6. Generate reports by adding --output html or --output json to the run command.

Exit Codes

All commands follow a consistent convention:

Exit CodeMeaning
0Success — all validations passed, all scenarios passed
1Failure — at least one validation error or at least one scenario failed

This makes it straightforward to integrate AgenticAssure into CI/CD pipelines and shell scripts where non-zero exit codes indicate failure.

What’s Next

Last updated on