Back to browse
GitHub Repository

OpenAPI-native testing platform with built-in environment management, flexible reporting (CLI/Web/Grafana), and zero-configuration setup.

1 starsGo

VolcAPI run your OpenAPI spec as a test suite from the terminal

by aliamer99·Apr 18, 2026·1 point·1 comment

AI Analysis

●●SolidShip ItSolve My Problem

Single source of truth beats drifting Postman collections, but early alpha.

Strengths
  • Custom v-functional-test extension embeds scenarios directly in OpenAPI YAML
  • Go binary with no runtime dependencies drops cleanly into CI pipelines
  • Environment configs handle local/staging/prod without separate files
Weaknesses
  • JUnit XML output still in progress—can't use in GitHub Actions yet
  • Only 1 star; author explicitly asking if concept is worth building
Target Audience

Backend engineers and API developers maintaining OpenAPI specs

Similar To

Schemathesis · Dredd · Postman

Post Description

I got tired of maintaining two files that describe the same thing: an OpenAPI spec for documentation and a Postman collection for testing. They always drift. Someone updates the spec, forgets the collection. A new engineer joins and runs outdated tests against an endpoint that was changed two months ago.

VolcAPI lets you define test scenarios directly inside your OpenAPI spec using a custom extension (v-functional-test), then run them from the CLI. Single source of truth.

It's a Go binary no runtime, no node_modules. The goal is for it to drop into GitHub Actions with zero friction once JUnit XML output lands (in progress).

Repo: https://github.com/aliamerj/volcapi

This is early alpha. GET/POST/PUT/DELETE work, response validation works, environment configs work. CI output formats are the next thing I'm building.

Honest question for the HN crowd: is the "spec as test suite" concept something you'd actually use, or do you prefer keeping tests separate from the spec? I've gone back and forth on this and would genuinely like to hear from people who've felt this pain.

Similar Projects

Developer Tools●●Solid

Turn any OpenAPI spec into agent-callable skills

It extracts focused, executable operations from giant OpenAPI files (the GitHub REST YAML is shown) to shrink context and avoid sidecar adapter sprawl — a pragmatic answer to token bloat and brittle ad-hoc integrations. Useful and concrete: if it actually generates tidy, updateable skill units and runtime hooks it saves a lot of maintenance. That said, the idea competes with existing LangChain/openai-function patterns; the repo will need clear runtime, versioning, and update strategies to feel like more than a nicer converter.

Solve My ProblemNiche Gem
yz-yu
103mo ago