Blog / Author
Jason Nguyen
Founder, Testsy
Jason Nguyen founded Testsy and builds it: the web and mobile test engines, the dashboard and this site. He writes here about the problems Testsy catches and how to check for them.
How these posts are made
Posts are written with AI help and checked against Testsy itself. The screenshots, recordings and results in a post come from Testsy runs, and the setup commands and numbers come from the same source as the docs, so they stay current.
Found a mistake? Write to contact@testsy.dev.
Posts
- Testing an app you built with AI: a guide for founders
- Find the bug before your client does: a guide for agencies
- Release testing for product teams: a guide
- Mobile release testing: a guide for app teams
- Your coding agent said “done”. Here is what it did not check
- Sign-up email links to localhost? Catch it before your users do
- It works in preview and breaks in production. Test the live address
- Fix one bug without breaking another: one bug, one test
- Turn a failed test into a fix prompt for your coding agent
- Let Cursor check its own work in a real browser
- Let Codex check its own work in a real browser
- Test from Gemini CLI, the Claude desktop app and claude.ai
- Test a Lovable, Bolt or Replit app by its address, no code needed
- Saved, then gone after a refresh: test that your app really saves
- Test that one user cannot see another user's data
- Test password reset from the email to the new password
- Catch the blank white screen after a deploy
- Ten tests to run before you share your AI-built app
- Write a test without writing code: steps, checks and values
- What an AI tester cannot check for you
- Test every Vercel preview before you merge
- Test Stripe checkout and plan upgrades in test mode
- Run browser tests after every deploy with GitHub Actions
- Tests that survive a redesign: why selector tests break
- Check AI-written code before your customers do
- Run plain-language browser tests in GitLab CI
- Run browser tests from any CI with one file
- Run your key journeys against production every night
- Send test failures to Slack, with the proof attached
- Send test results to Linear or Jira with webhooks
- Test team invitations from the email to the joined workspace
- Test admin and member roles: what each person can see and do
- Release checks for a startup with no QA team
- Flaky tests, and what a test verdict should be allowed to say
- What a browser test suite costs when you pay per run
- Test search, filters and sorting without hard-coding the data
- Turn your release checklist into tests that run themselves
- Check the numbers: totals, prices and counts on screen
- Test receipts, notifications and other emails your app sends
- Share a live test run in a pull request, no account needed
- A website launch QA checklist for agencies, with tests that run
- Test a contact form all the way to the inbox
- Check forms and checkout after every WordPress plugin update
- Test Shopify add to cart and checkout after an app or theme update
- Test a booking form or calendar embed from start to confirmation
- Show clients proof, not screenshots
- Organise testing for many client sites: one project per client
- Add functional checks to a website care plan
- Test a site at phone, tablet and desktop sizes
- Test form validation messages, not only the happy path
- Test redirects after a site redesign or migration
- Test a newsletter signup with double opt-in, end to end
- Test a cookie banner: accept, decline, and the choice sticking
- A handoff record that proves the site worked at launch
- Give clients a viewer seat to see their test results
- When bot protection blocks your tests, and how to allow them
- Test a multilingual site and its language switcher
- Pass App Store review: test what the reviewer will do first
- Test an Expo app in CI without rebuilding it every time
- Build an Android APK that runs on cloud test devices
- Build an iOS app for cloud testing: a zipped Simulator .app
- Test a React Native app in plain English, without test IDs
- Test a Flutter app on iPhone and Android, canvas included
- Test mobile onboarding and the first launch, on a fresh install
- Test your app's iPad layout and landscape, not only the phone
- One test for iPhone and Android: write it once, run it on both
- Test a chat or marketplace app with two phones in one test
- Let your coding agent test the mobile app it just built
- Mobile tests that survive a redesign
- Sign in to a mobile app in a test without the password in the test
- Import app builds from EAS, Bitrise or S3 by link
- Test a Capacitor or Ionic app: native shell, web content
- Sign-up emails that stop arriving after launch
- Paid, but still on the free plan: test the Stripe webhook
- Uploads that work for you and fail for your users
- Test your app as a brand-new user, not as yourself
- Test that a double click does not create two orders
- Test that a multi-step form keeps answers when users go back
- Run tests in production without polluting your data
- Test both sides of a feature flag before you flip it
- Upgrade a framework without breaking what users do
- Write tests in your team's own language
- Check the record was saved, not just the success message
- Test a WooCommerce checkout after every update
- After moving a site to a new host, check the forms still send
- Test what visitors in another country see
- Test a lead magnet from the form to the inbox to the file
- Test a membership site: members in, everyone else out
- What survives when a user deletes and reinstalls your app
- Find unlabeled buttons and tiny tap targets in a mobile app
- Test the Android Back button after the Android 16 change
- The keyboard covers the text field on Android 15 and 16
- Test what users see when a request fails
- Sign in with Google works locally and fails in production
- Test gestures in a mobile app: long press, swipe, drag and pinch
- Test a long list on Android: scroll, swipe to delete, pull to refresh
- “Coupon applied” is not a discount: test the total, not the message
- Test photo and file pickers in a mobile app
- Test the phone menu on a client site after every update
- Test the files your mobile app exports, downloads and shares
- The hardest parts of web testing, each one run for real
- Test a form inside an iframe, Shadow DOM and a new tab
- Test what is inside a download: CSV, Excel, PDF and ZIP
- Test file uploads: a good file, a fake one and one too big
- Test drag and drop, resizing and drawing on a canvas
- Test alert, confirm and prompt, and the browser's permission prompts
- Test that sign-in and saved data survive a reload
- Test slow pages and failed requests without a single sleep
- One web test across a frame, an upload, a second tab and a download
- Test that a video really plays, and what the page says when it cannot
- Test date pickers, hover, right-click menus and keyboard shortcuts
- Test email verification codes, the wrong code and the resend too
- Test an admin site and a public site, as two people, in one test
- The hardest parts of mobile app testing, each one run for real
- Test that a notification opens the right screen
- Test what your app does when the user says no to a permission
- Test SMS code sign-in on Android without a second phone
- Test deep links: does the link open the right screen?
- Test Face ID unlock: the wrong face, then the right one
- Test what your app remembers after the phone kills it
- A mobile app crash, caught with the file and line that caused it
- Test your app offline, on low battery and during a phone call
- Test rotation, dark mode and the largest text size
- Test location features without leaving your desk
- Test a Live Activity and a home-screen widget on iPhone
- One mobile test, six OS versions: what changed on screen
- Moving from TesterArmy to Testsy before 15 January
- Making an AI tester prove its verdicts
- Make Claude Code test what it just built
- Test sign-ups that send an email or SMS code
- A daily check on every client site's key flow
- Five AI testers, one planted bug: what each verdict rested on