Overview
What Tarn is, what problems it solves, and how it compares to Postman, curl, Hurl, and Playwright.
YAML-simple test authoring. Structured JSON failures with stable error codes and remediation hints. MCP tools. One binary, zero runtime dependencies.
Tarn's wedge is not "YAML tests exist." It is that failures come back as structured data with a stable taxonomy an agent can reason over.
Every failure includes a category, error code, and remediation hints. Agents branch on taxonomy, not regex.
tarn-mcp exposes list, validate, run, and fix_plan as structured tools. No stdout scraping needed.
JSONPath, status shorthand, type checks, UUID validation, date matching, schema validation, and unified diffs.
Type-preserving captures from JSONPath, headers, cookies, regex, status, and URL. Chain with transforms.
Automatic cookie jar by default. Named jars for multi-user session testing. Per-step disable switch.
Poll until assertions pass. Step-level retries for transient failures. Configurable intervals and limits.
tarn-lsp is a standalone LSP 3.17 server. VS Code extension and Claude Code plugin on top. Diagnostics, hover, completion, code lens, quick fixes.
--ndjson emits one event per line for live UIs. --select file::test::step ANDs with --tag for surgical reruns. --only-failed keeps tight iteration.
tarn fmt normalizes YAML aliases and field order. --check mode fails in CI when files drift.
Optimized for onboarding. The repository markdown remains the deeper source for strategy and workflow details.
What Tarn is, what problems it solves, and how it compares to Postman, curl, Hurl, and Playwright.
Install Tarn, scaffold a project, run your first test, and understand the core loop — fmt, validate, run.
Complete guide to YAML test files: requests, assertions, captures, variables, cookies, multipart, includes, and built-in functions.
Full reference for all tarn commands: run, validate, format, list, init, bench, lint, scaffold, and more.
Structured JSON output, failure categories, fix plans, and agent loops for AI-driven test development.
Portable .mcp.json setup for Claude Code, opencode, Cursor, Windsurf — structured tools for agents.
Standalone LSP server for diagnostics, hover, completion, code actions, and JSONPath evaluation in any editor.
GitHub Actions, environment secrets, artifact reports, format gating, and best practices for CI pipelines.
Copy-paste ready test files: health check, CRUD, auth flow, faker data, and the local demo-server suites.
Common issues and fixes: parse errors, connection failures, capture problems, assertion mismatches, and more.
Compact reference pages: assertion operators, built-in functions, YAML format, JSON report, failure categories, MCP tools, LSP capabilities.
Full source, strategy docs, roadmap, comparison matrix, and release notes.