Reference pages
Assertion Operators
All 30+ operators for body, status, headers, duration, redirects
Built-in Functions
UUIDs, timestamps, faker, random generators, determinism
YAML Test File Format
All fields: top-level, step, request, assert, capture, poll, include, auth
JSON Report Format
Report schema, step object, JSON modes, CI parsing guide
Failure Categories
assertion_failed, connection_error, timeout, parse_error, capture_error
MCP Tools
tarn_run, tarn_validate, tarn_list, tarn_fix_plan parameters and agent loop
LSP Capabilities
Feature matrix, sidecar convention, supported editors
JSON Schemas
The canonical JSON schemas define the exact grammar for test files and reports:
schemas/v1/testfile.json— Schema for.tarn.yamlfilesschemas/v1/report.json— Schema fortarn run --format jsonoutput
Add this comment to the top of your test files for IDE autocompletion:
# yaml-language-server: $schema=https://raw.githubusercontent.com/NazarKalytiuk/tarn/main/schemas/v1/testfile.json
Configuration reference
tarn.config.yaml fields:
| Field | Default | Description |
|---|---|---|
test_dir | "tests" | Directory to scan for .tarn.yaml files |
env_file | "tarn.env.yaml" | Default env file name |
timeout | 10000 | Global default timeout in milliseconds |
retries | 0 | Retry failed requests |
parallel | false | Parallel file execution default |
fail_fast_within_test | false | Abort remaining steps on first failure |
faker.seed | — | 64-bit seed for deterministic RNG |
proxy | — | Explicit proxy URL |
insecure | false | Disable TLS verification |