I've been building QAPIR (https://app.qapir.io), an attempt to put most backend testing tools into one place instead of stitching together test code, frameworks, reporting tools, client libraries, mock servers, etc.
Today it focuses on REST APIs.
You can point it at an OpenAPI spec or let it crawl your API docs. It extracts endpoints and generates ready-to-run API test scenarios automatically. In about 2–3 minutes you get a working baseline test suite with environment variables, secrets, and test reports.
Scenarios are written in a concise YAML format (with a structured UI editor if you don't want to touch YAML). They support response extraction, validations, environment variables/secrets, and chained calls.
Where I want to take it next:
- CI integrations (GitHub / GitLab Actions)
- more protocols (GraphQL, WebSockets, gRPC)
- more test steps like DB/cache queries, event queues, HTTP mocks, and webhook testing
The idea is that backend testing shouldn't require maintaining large test codebases or wiring together numerous tools to cover most (or all) scenarios.
It's early and rough. Free plan when you sign up includes 3 workspaces, 3 doc crawl jobs, and 100 test runs - enough to try it on a real service.
Feedback I'd love from HN:
- what's missing for your stack?
- is the workflow simple enough?
- if you find it interesting, feel free to join the beta.
Thanks for taking a look,
Albert
cebert•1h ago
gradnichkovski•27m ago
Now you can sign up, paste a link to your API docs, and get a working test suite in a couple of minutes. Plus run it in cloud.
This change completely removes the setup and gives more out of the box. The goal of this post is to show that new workflow and get feedback on it.