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/volcapiThis 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 ...