BlogTopic
Testing forms, bookings and checkout
The journeys that earn the money: a booking form, a cart, a checkout, and the widgets inside them.
GuidesWebTest a Lovable, Bolt or Replit app by its address, no code neededBuilt your app in Lovable, Bolt, Replit or v0? Paste the published address, describe a user's journey in plain words, and get a verdict with a replay.2 min read
GuidesWebTest Stripe checkout and plan upgrades in test modeBilling bugs cost money twice. A plain-language test goes through Stripe Checkout in test mode, comes back and checks the plan changed, plus declines and 3D Secure.2 min read
GuidesWebCheck the numbers: totals, prices and counts on screenA page that loads is not a page that is right. Make checks read the actual total, price or count, and keep the value the verdict was decided on as evidence.2 min read
GuidesWebA website launch QA checklist for agencies, with tests that runForms, checkout, redirects, phone layouts and email: the launch checks agencies list every time, written as plain-language tests to run before handoff and after.2 min read
GuidesWebTest a contact form all the way to the inbox“Message sent” on the page proves nothing. How to test that a form's confirmation email arrives and the submission reaches the owner, with a run that has its own mailbox.2 min read
GuidesWebTest Shopify add to cart and checkout after an app or theme updateAn app install or theme update can silently break the cart. A plain-language test adds a variant, reaches checkout and pays with Shopify's test gateway, on a schedule.1 min read
GuidesWebTest a booking form or calendar embed from start to confirmationBookings run through date pickers, embedded widgets from another company and confirmation emails. One plain-language test books a slot and checks every step.2 min read
GuidesWebTest a site at phone, tablet and desktop sizesMost visitors arrive on a phone, and most QA happens on a laptop. Run the same plain-language test at 412 × 914, 820 × 1180 and 1280 × 800 and compare.2 min read
GuidesWebTest form validation messages, not only the happy pathAn empty or mistyped form should say what is wrong, where. A plain-language test submits it empty, reads the exact error, then completes it and reads the saved result.1 min read
GuidesWebTest a newsletter signup with double opt-in, end to endA signup form that says “check your inbox” proves nothing until the confirmation email arrives and its link works. One test signs up, confirms and checks the welcome.1 min read
GuidesWebTest that a double click does not create two ordersA slow Pay button gets clicked twice and the customer is charged twice. Test what a hurried person does, then check exactly one order exists, not the thank-you page.2 min read
GuidesWebTest that a multi-step form keeps answers when users go backStep 3 of a checkout or sign-up, the user presses Back to fix step 1 and finds every answer gone. One plain-language test goes back and forth and checks each value.2 min read
GuidesWebWrite tests in your team's own languageTests in Spanish, Vietnamese or German, with the plan and results in that language and the screen's text kept as it is. Two real runs, and the lesson one of them taught.3 min read
GuidesWebCheck the record was saved, not just the success messageA thank-you message proves the page changed, not that anything was stored. Check the record on screen, or read your system through an endpoint you define.2 min read
GuidesWebTest a WooCommerce checkout after every updateWooCommerce, payment plugins and the theme update on their own schedules, and the checkout is where they collide. A nightly test places an order and checks it arrived.2 min read
GuidesAndroidThe keyboard covers the text field on Android 15 and 16Apps targeting Android 15 draw edge to edge and the window no longer resizes for the keyboard, so fields end up behind it. A real run checks the field stays visible.2 min read
GuidesAndroid“Coupon applied” is not a discount: test the total, not the messageAn app says the coupon was applied and charges full price. A real Android run caught exactly that, because the check was on the subtotal, not on the message.2 min read
GuidesWebTest email verification codes, the wrong code and the resend tooA sign-up test that stops at "we sent you a code" proves little. Two real runs read the email, try a wrong code, ask for a new one and finish signing up.5 min read
GuidesWebA daily check on every client site's key flowClients find out their booking form is broken from their customers. Set up one scheduled test per site, get told when it fails, and send the client the proof.4 min read
GuidesWebTest Stripe checkout and plan upgrades in test modeBilling bugs cost money twice. A plain-language test goes through Stripe Checkout in test mode, comes back and checks the plan changed, plus declines and 3D Secure.2 min read
GuidesWebCheck the numbers: totals, prices and counts on screenA page that loads is not a page that is right. Make checks read the actual total, price or count, and keep the value the verdict was decided on as evidence.2 min read
GuidesWebA website launch QA checklist for agencies, with tests that runForms, checkout, redirects, phone layouts and email: the launch checks agencies list every time, written as plain-language tests to run before handoff and after.2 min read
GuidesWebTest a contact form all the way to the inbox“Message sent” on the page proves nothing. How to test that a form's confirmation email arrives and the submission reaches the owner, with a run that has its own mailbox.2 min read
GuidesWebTest Shopify add to cart and checkout after an app or theme updateAn app install or theme update can silently break the cart. A plain-language test adds a variant, reaches checkout and pays with Shopify's test gateway, on a schedule.1 min read
GuidesWebTest a booking form or calendar embed from start to confirmationBookings run through date pickers, embedded widgets from another company and confirmation emails. One plain-language test books a slot and checks every step.2 min read
GuidesWebTest a site at phone, tablet and desktop sizesMost visitors arrive on a phone, and most QA happens on a laptop. Run the same plain-language test at 412 × 914, 820 × 1180 and 1280 × 800 and compare.2 min read
GuidesWebTest form validation messages, not only the happy pathAn empty or mistyped form should say what is wrong, where. A plain-language test submits it empty, reads the exact error, then completes it and reads the saved result.1 min read
GuidesWebTest a newsletter signup with double opt-in, end to endA signup form that says “check your inbox” proves nothing until the confirmation email arrives and its link works. One test signs up, confirms and checks the welcome.1 min read
GuidesWebTest that a double click does not create two ordersA slow Pay button gets clicked twice and the customer is charged twice. Test what a hurried person does, then check exactly one order exists, not the thank-you page.2 min read
GuidesWebTest that a multi-step form keeps answers when users go backStep 3 of a checkout or sign-up, the user presses Back to fix step 1 and finds every answer gone. One plain-language test goes back and forth and checks each value.2 min read
GuidesWebWrite tests in your team's own languageTests in Spanish, Vietnamese or German, with the plan and results in that language and the screen's text kept as it is. Two real runs, and the lesson one of them taught.3 min read
GuidesWebCheck the record was saved, not just the success messageA thank-you message proves the page changed, not that anything was stored. Check the record on screen, or read your system through an endpoint you define.2 min read
GuidesWebTest a WooCommerce checkout after every updateWooCommerce, payment plugins and the theme update on their own schedules, and the checkout is where they collide. A nightly test places an order and checks it arrived.2 min read
GuidesAndroidThe keyboard covers the text field on Android 15 and 16Apps targeting Android 15 draw edge to edge and the window no longer resizes for the keyboard, so fields end up behind it. A real run checks the field stays visible.2 min read
GuidesAndroid“Coupon applied” is not a discount: test the total, not the messageAn app says the coupon was applied and charges full price. A real Android run caught exactly that, because the check was on the subtotal, not on the message.2 min read
GuidesWebTest email verification codes, the wrong code and the resend tooA sign-up test that stops at "we sent you a code" proves little. Two real runs read the email, try a wrong code, ask for a new one and finish signing up.5 min read
GuidesWebA daily check on every client site's key flowClients find out their booking form is broken from their customers. Set up one scheduled test per site, get told when it fails, and send the client the proof.4 min read