​

Replay

​

How It Works

YAML File  →  Parser  →  State Bag  →  Templating  →  Runners  →  Assertions  →  Reporter

1. Parser loads your YAML workflow into a typed Go structure
2. State Bag stores variables shared across all steps
3. Templating replaces {{ var }} placeholders before execution
4. Runners execute the step (HTTP, DB, Shell, Print)
5. Assertion Engine validates outcomes with JSONPath-based checks
6. Reporter prints coloured pass/fail results

​

Example

name: user-onboarding
config:
  http:
    base_url: https://api.example.com
steps:
  - name: login
    type: http
    request:
      method: POST
      url: /auth/login
      body:
        email: qa@example.com
        password: pass123
    extract:
      token: $.data.token
    assert:
      - ["$.status", "eq", 200]

  - name: verify-user-in-db
    type: db
    query: SELECT id FROM users WHERE email = 'qa@example.com'
    extract:
      user_id: $[0].id
    assert:
      - ["$[0].id", "not_null"]

​

Key Features

• 7 step types — HTTP, DB (PostgreSQL/Redis), Shell, Print, Loop, Call (cross-file), If (conditional)
• Stateful variables — Extract values from any step and reuse them in later steps via {{ var }}
• JSONPath extraction & assertions — Target nested fields in JSON responses
• 45 built-in template functions — String, math, date, JSON manipulation, type conversion
• Parallel execution — Run multiple workflows concurrently with --concurrency N
• Watch mode — Auto-re-run workflows on file changes during development
• Config profiles — Switch between dev, staging, and prod configs with --profile
• Deterministic — Same inputs produce the same results, every run

​

Quick Links

• Quickstart — Run your first workflow in 60 seconds
• Installation — Install via Go, binary, or Docker
• Writing Workflows — Core concepts and DSL syntax
• Use Cases — Real-world scenarios for QA and dev teams