In this video· click a step to jump to it
Test recording
QuotaMint — app walkthrough
82,681 ms · 1,664,293 pixels changed
We built this regression test for www.quotamint.com — it's yours to keep, free.
Take this test with you
This is a real Playwright test, recorded against www.quotamint.com. Claim it into your own workspace and re-run it on every deploy — free.
export async function test(page, baseUrl, screenshotPath, stepLogger) {
const PLAN_ID = '0825ab39-3d55-46e2-983d-b479f2644294';
const STAMP = Date.now().toString(36);
let n = 0;
const shot = async (slug) => {
n += 1;
await page.waitForTimeout(600);
await page.screenshot({ path: `${screenshotPath}/Step_${n}_${slug}.png`, fullPage: true });
stepLogger.log('captured ' + slug);
};
stepLogger.log('Public 1: landing page');Checks run
Notes from the demo run
AI-generatedWe signed up for QuotaMint, ran your five-step setup, and then drove the Test workspace end to end: overview, customers, plans, features, usage, API keys, developers, audit log, account plan and settings. The Test/Live split is the strongest thing here - every page tells you which environment's data you are looking at, and the create-customer dialog explicitly warns that the same customer ID in the other environment is a different customer. We created a real customer on the Starter plan during the run.
- Test/Live is never ambiguousThe environment pill sits next to the project switcher on every page, and Customers repeats it in the page subtitle. Most usage-metering tools make you guess which dataset you are in.
- The overview doubles as a setup checklist'2 of 5 steps complete for Test' with an Open link per remaining step meant we always knew the next action without reading docs.
- Setup ends with a runnable curlStep 5 of onboarding hands you the exact POST /v1/consume call with your feature key already filled in, so the first integration attempt is copy-paste.
- Create account drops you back on the sign-in formSubmitting the signup form redirected to /login with no success message, so we typed the same email and password a second time. Signing the new session in directly would remove a step right at the moment of highest intent.
- Onboarding step 1 failed once with a generic errorThe first 'Name your workspace' Continue returned ERR_CONNECTION_CLOSED on the server action and rendered 'This page couldn't load - your data has not been changed'. Retrying worked. A retry-with-backoff on that action, or naming the failing step, would stop a first-run user assuming the product is broken.
- /api-keys create flow·We viewed the page but did not mint a Test key - we do not generate live credentials on a recording.
13 visual changes
Share this run
Proof your app is not AI slop
This test was built for www.quotamint.com — claim it free
One click copies the test and baseline screenshots into your own Lastest workspace. Re-run on every deploy and catch regressions before your users do — free, no card required.