Try TestingForge with one click.
A fully working workspace pre-loaded with the TestingForge Demo scenario and a self-contained sandbox API. No signup, no credit card, no install.
- Run the TestingForge Walkthrough scenario end-to-end and watch the live trace.
- Inspect ~25 pre-built bricks covering auth, polling, retries, multipart, webhooks, and assertions.
- Hit the in-process
/demo-api/*sandbox so you don't need an external test target. - See exactly which actions a public demo can — and can't — do.
The workspace resets every 60 minutes.
Anything you create here — bricks you edit, runs you launch, items in /demo-api — disappears on the next reset.
Next reset countdown loads above the navbar after sign-in.
What's inside
- Scenario
demo_walkthrough: smoke → auth → CRUD → body modes → reliability → async → uploads → webhooks → teardown. - Self-contained sandbox at
/demo-api/*:/health,/version,/items,/jobs,/upload,/flaky,/slow,/errors/{code}. - Pre-set
E2E_USER_*options so the auth bricks just work. - One demo domain pinned to
https://testingforge.io.
What's locked down
- You cannot edit/delete bricks, scenarios, secrets, domains, members, billing, SCM, Slack.
- Runs only target the in-process sandbox — outbound HTTP to other hosts is forced back to
https://testingforge.io. - CI pipeline endpoints (
POST /ci/runs) and Slack/Stripe notifications are silently skipped. - Hard caps on demo runs, items and jobs prevent resource abuse.
Rules of the road
The demo account is shared by everyone visiting https://testingforge.io/demo. Treat it like a public whiteboard: feel free to draw on it, just don't be surprised when someone wipes it.
If you want a private workspace, the free signup takes about a minute and your scenario stays yours.
Ready for your own workspace?
Connect your repo, generate a scenario from real endpoints, and run it in CI. No demo limits, full retention.