CLI Reference

Overview

The Test Orchestration Command-Line Interface (CLI) enables you to create, manage, and execute workflows programmatically. It's ideal for automation, CI/CD integration, and scripting.

circle-info

💻 Command Line Power

CLI capabilities:

  • Create and manage projects

  • Define and execute workflows

  • Configure execution settings

  • Retrieve results and reports

  • Automate common tasks

  • Integrate with CI/CD systems


Installation

macOS

brew install test-orchestration

Linux

Windows

Verify Installation


Basic Commands

Help and Information

Project Commands

Workflow Commands


Authentication

API Token

Login

Logout


Workflow Execution

Execute Workflow

Monitor Execution

Cancel Execution


Configuration

Configuration File

Environment Variables

Configuration File Locations


Output Formats

Default (Table)

Output:

JSON Output

Output:

CSV Output

Output:

YAML Output


Data Import/Export

Export Workflow

Import Workflow

Backup and Restore


Scripting Examples

Execute Workflow and Get Results

Batch Execute Workflows

CI/CD Integration (GitHub Actions)

Create Project and Workflow


Advanced Options

Logging and Debugging

Performance Tuning

Custom Headers


Troubleshooting CLI

Common Issues

Command not found

Authentication failed

API connection error


Command Quick Reference

Command
Purpose

to-cli project list

List all projects

to-cli workflow list --project ID

List workflows

to-cli workflow execute ID

Execute workflow

to-cli workflow status ID

Check status

to-cli workflow watch ID

Monitor execution

to-cli config show

Show configuration

to-cli auth verify

Verify authentication

--help

Show command help

--output json

JSON output format

--verbose

Verbose output


Best Practices

✅ Do

  • Use environment variables - Secure credential storage

  • Store tokens safely - Don't hardcode in scripts

  • Use JSON output - For parsing in scripts

  • Set timeouts - Prevent hanging executions

  • Log executions - For debugging and auditing

  • Version control scripts - Track CLI automation

  • Test locally first - Before CI/CD integration

❌ Don't

  • Hardcode API tokens - Use env variables

  • Store credentials in git - Use secrets management

  • Ignore error codes - Check exit codes in scripts

  • Run without timeouts - Could hang indefinitely

  • Assume JSON structure - Parse with jq/grep

  • Mix credentials - Use one auth method



Summary

  • CLI provides command-line automation

  • Install via package manager or download

  • Authenticate with API token or login

  • Execute workflows via workflow execute command

  • Configure via config file or environment variables

  • Script for automation and CI/CD


Next: Learn about Glossary for terminology.

Last updated