You give us the repo. We build your API workflows.
TestingForge reads your repository, maps the real flows through your APIs, and generates a complete, editable test suite — scenarios, groups, bricks, variables, and assertions. No empty collection to fill in by hand. On day one you have something to run.
Point us at your repository Connect
Paste a GitHub or GitLab URL and pick the environments you already have. That's all we ask for — TestingForge figures the rest out from your code, OpenAPI, and real HTTP traffic.
Connect a repository
We read your code, OpenAPI, and recorded traffic — nothing is pushed, nothing is changed.
We build your suite — not you Auto-generate
In a few minutes you have real scenarios, groups, bricks, variables, secrets and assertions — all wired together. You review and tweak; you don't start from an empty collection.
github.com/acme/storefront-api
Finished in 3m 12s · nothing pushed to your repo
What we did
- ✓Discovered 147 endpoints from OpenAPI + 23 more by static analysis of your handlers.
- ✓Clustered them into 12 scenarios — Checkout, Auth, Catalog, Payments, Admin, Webhooks…
- ✓Wired 38 runtime variables (accessToken, userId, cartId, orderId…) between calls automatically.
- ✓Synthesized 214 assertions — status codes, JSON shape, response time, key headers.
- ✓Linked 6 secrets from your vault (API keys, service tokens) — values stay masked.
Generated scenarios
- Auth flows14 bricks
- Catalog & search22 bricks
- Checkout smoke8 bricks
- Payments & refund17 bricks
- Admin & orders31 bricks
- Webhooks9 bricks · async
- + 6 more scenarios
Sign in to the workspace we prepared Login
Your team members log in to a workspace that's already populated — scenarios, bricks, environments, secrets. Nothing blank, nothing to set up by hand.
Command Center, already wired up Dashboard
From the first login: driver status, live KPIs, 24-hour activity and a plain-English health verdict. This data is flowing because your scenarios are already running — they didn't wait for you to write them.
Acme
Main issue None in the last 6h.
Impact No critical flows affected.
Suggested action Keep nightly regression scheduled.
0 failed · success rate 98% · last 6h
Recent activity (24h)
- 42 runs finished
- 2 failed
- 95% success rate (finished)
Trend vs prior 24h: improving
Every run of your generated suite Logs
CI, schedule, manual — every execution of the suite we built for you lands here. Filter by status, date or text; jump into any run's full trace in one click.
Your generated bricks — editable, not frozen Bricks
The bricks below aren't something you wrote. We wrote them for your repo. But — unlike a generated black-box — every brick is a plain record you can rename, reorder, tweak, disable or fork. The amber groups are ones your team edited on top of our baseline.
Bricks
Checkout smoke
Trace every call, not just the last error Run
Each row is a real HTTP call in Swagger-UI verb colors. Expand a failing brick to see the request, the response, and the exact assertions that broke — then copy as cURL or re-run just the failed ones. This is what "transparent, not a black-box" actually looks like.
Checkout smoke · Run #5127
Response body · brick "Create order"
{
"error": "promo_invalid",
"message": "Promo code EXPIRED has expired",
"status": "rejected"
}
Failed checks
201 — got 422$.data.status equals confirmed — got "rejected"800ms (389 ms)Point us at your repo — and see it running by tomorrow morning
Connect a GitHub or GitLab repository, and on the other side you get a structured suite of scenarios, bricks and assertions that's actually runnable. No collection-building homework. You still own it — every brick is a plain, editable record.