Back to browse
Dochia – automated API testing for agentic build-test-fix loops

Dochia – automated API testing for agentic build-test-fix loops

by ludovicianul·Apr 2, 2026·2 points·1 comment

AI Analysis

●●●BangerBig BrainWizardrySolve My Problem

120+ built-in test playbooks with JSON output agents can read and fix.

Strengths
  • Agent-actionable report format lets coding agents fix failures without human parsing.
  • Native GraalVM binary runs fast across macOS, Linux without runtime dependencies.
  • Focuses on negative and boundary cases that traditional tools miss.
Weaknesses
  • API testing space has Postman, Schemathesis, and pytest already established.
  • Requires OpenAPI spec — won't help with undocumented or legacy APIs.
Target Audience

Backend engineers, API developers, QA engineers

Similar To

Schemathesis · Postman · Dredd

Post Description

I've enhanced Dochia with the ability to generate agent skills. Being a CLI already, it makes it really simple to plug it into agentic workflows.

Run `dochia init-skills` and the coding agent(s) can trigger tests as it builds:

1. Agent writes endpoint and the OpenAPI spec (or that get's generated from code) 2. Agent runs: dochia test -c api.yml -s localhost:3000 3. Dochia produces dochia-summary-report.json + per-endpoint test files 4. Agent reads errors, fixes code, re-runs 5. Loop

The JSON output is structured specifically so agents can read and act on it directly, not just humans parsing logs.

It's a native binary (GraalVM), so it's fast on all platforms.

Would love feedback on: is it something you will integrate into your flow, which test playbooks are missing, whether the report format is actually useful in agentic loops, any edge cases you'd expect a tool like this to catch?

GitHub: https://github.com/dochia-dev/dochia-cli Docs: https://docs.dochia.dev

For background, Dochia takes your OpenAPI spec and runs 120+ test playbooks: deterministic negative and boundary scenarios plus chaos testing. No test cases to write, no configuration beyond pointing it at your OpenAPI spec and a running server.

Similar Projects