Practise modern testing on systems that behave like the real thing.
AI is accelerating how fast software gets built. The ability to prove that it works end to end has to keep pace. testthis.now hosts deliberately realistic, integrated applications where teams can experiment, learn and practise AI-enabled testing skills, in a safe environment where nothing is real and nothing can be broken that matters.
Delivery got faster. Verification has to catch up.
AI coding assistants and agents now produce features, integrations and tests at a pace no review process was designed for. The bottleneck has moved from writing software to knowing, with evidence, that it does what the business needs.
More change, less time to check it
When code arrives faster, every release carries more change. Teams need testing that is automated, repeatable and fast enough to sit in the pipeline, not a phase at the end.
The risk lives between the components
Unit tests generated alongside the code tend to share its blind spots. Real failures hide in the journeys: sign-up, email codes, MFA, payments, fulfilment, and the back office that picks up the pieces.
AI changes the tester's toolkit
Agents that drive browsers, generate test data, read requirements and propose test cases are powerful, but they need direction, guardrails and a human who knows what good evidence looks like.
Skills need a practice field
You cannot learn this on production, and a to-do list or a one-page sign-up form will not teach it. Practice needs state, integrations, rules and consequences, without real customers or real money.
What you can practise here
Every app on testthis.now is a system under test, built to reward the techniques that matter in AI-accelerated delivery.
- AI-assisted test designTurn business rules into scenarios and edge cases with an assistant, then check its work.
- Agent-driven end-to-end automationPoint Playwright, Selenium or an MCP-connected agent at a real multi-step journey.
- Out-of-band stepsAutomate emailed verification codes and TOTP MFA instead of skipping them.
- API testing behind authenticationExercise JWT-secured APIs and compare them with what the UI shows.
- Test data strategyCreate, pool, reuse and isolate data so parallel runs never collide.
- Time-dependent behaviourMove the clock forward to test deliveries, status changes and cover periods.
- Cross-application verificationAct as a customer, then confirm the outcome from the staff side.
- Negative and unhappy pathsDeclined payments, expired codes, password resets and support complaints.
- Pipelines and performanceRun suites from CI and put realistic journeys under load.
The apps
Apps are versioned in their hostnames, so a version stays put once published. Scripts written against v1 keep working when v2 arrives alongside it.
Verdant Dock, version 1
A retailer of self-moving auto planters and the exotic plants that live in them. Verdant Dock is a connected business rather than a single screen: a customer storefront and a staff portal share the same orders, deliveries, insurance cover and support cases, with real email in the loop.
Verdant Shop
- Sign-up with emailed code and mandatory TOTP MFA
- Password reset and JWT-secured APIs
- Planters and plants in matched sizes, with sizing rules
- Mock card payments with deterministic declines
- Product insurance, cover activation and a bundled expert check-in
- Truck delivery scheduling within 150 km of Melbourne
- Date manipulation to fast-forward deliveries, clearly flagged as test data
- Support enquiries and complaints, with email updates
Verdant Staff
- Staff enrolment that mirrors customer sign-up
- Orders, deliveries and customers from your own test sessions
- Support case handling, with every update emailed to the initiator
- A second point of view to verify what the shop claims happened
- Ideal for end-to-end checks that cross the customer and back-office boundary
Verdant Warehouse
- Planned: picking, dispatch and stock for the same orders
- Extends journeys from purchase through to fulfilment
Why an integrated system beats a simple demo app
Most practice sites are a shopping cart or a sign-up form. They are fine for learning locators, but they cannot teach the problems that stall real automation programmes. Verdant Dock was built to include them.
| Capability | Typical demo app | Verdant Dock v1 |
|---|---|---|
| Identity | Username and password, often pre-filled | Emailed verification code, mandatory TOTP MFA, password reset, JWT sessions |
| None, or faked on screen | Real delivery. Use a testthis.now address and read codes through an API | |
| Payments | Always succeeds | Mock card processing with predictable declines for negative-path tests |
| Business rules | Add to cart, check out | Size matching, insurance, delivery radius, bundled service entitlements |
| Time | Everything happens instantly | Deliveries and cover progress over days, with a controllable test clock |
| Multiple actors | One user, one screen | Customers and staff in separate apps acting on the same records |
| After-sales | Ends at the confirmation page | Support cases raised by email or in-app, worked by staff, with notifications |
| Stability for scripts | Changes without notice | Versioned hostnames, so published versions do not move under your tests |
That is the difference between rehearsing a click path and rehearsing a release: the same practice run can cover authentication, messaging, money, time and the back office, which is exactly where AI-generated tests most need a knowledgeable human to check them.
A safe place to experiment
Everything here is invented, and it is meant to be poked, automated and occasionally broken.
No real money or goods
Payments are simulated and nothing ships. Use test card details only, never a real card.
Use invented data
The apps are public. Do not enter real personal information. Generated names, addresses and testthis.now mailboxes work best.
Your data stays with you
Records you create are separated from other visitors' activity. It is a convenience, not a security boundary, so treat everything as visible.
Be a good neighbour
Activity is logged with source addresses. Automation and moderate load are welcome. Anything that degrades the service for others is not.
testthis.now so verification codes can be read by your scripts, and generate TOTP codes from the secret shown during MFA enrolment.