How Do I Test My App? A Plain English Guide for Non-Developers.
You built your app with Claude, ChatGPT, Bolt, or Lovable and you want to make sure it keeps working as you make changes. Right now, every time you update…
You built your app with Claude, ChatGPT, Bolt, or Lovable and you want to make sure it keeps working as you make changes. Right now, every time you update something, you manually click through the app to check if it still works. This takes time, and you sometimes miss things. Testing is the practice of writing code that automatically checks your app works correctly. Here is what types of testing exist, which ones are worth your time, and how to add them without needing a testing background.
Why Testing Matters for Vibe-Coded Apps
When you make a change to your app, you want confidence that you have not accidentally broken something else. Manual testing by clicking through the app works but does not scale. As your app grows, the number of things to check grows too.
Automated tests are code that checks your code. You run them after making changes and they tell you whether everything still works. If you break something, the test catches it before your users do.
The Three Types of Tests Worth Knowing
Unit tests check individual functions in isolation. Does this specific function return the right value for a given input? Fast to write, fast to run, very targeted.
Integration tests check that different parts of your app work together correctly. Does the API endpoint return the right data when called with these parameters? Does the database update correctly when this action happens?
End-to-end tests simulate a real user clicking through your app. Open the browser, go to this page, click this button, fill in this form, verify this outcome appeared. Most comprehensive but slowest to write and run.
For most vibe-coded apps, start with integration tests on your most critical paths. What are the things that absolutely must work? Sign up, log in, the core feature your app exists to provide. Test those first.
How to Add Tests to Your App
Ask your AI: “I want to add automated tests to my app. Can you write integration tests for the most critical user flows: [describe them, e.g. user sign up, user login, creating a record, submitting a form]? Use [pytest for Python / Jest for JavaScript] and show me how to run them.”
Your AI will write test files that you can run with a single command. When you make future changes, running the tests tells you instantly whether anything broke.
End-to-End Testing With Playwright
Playwright is the most popular tool for end-to-end browser testing. It automates a real browser, clicking and typing as a user would.
Ask your AI: “Can you write Playwright tests for my app that simulate the most important user journeys? I want to test: [describe the journeys, e.g. a new user signing up and completing their first action]. Show me how to install Playwright and run the tests.”
Playwright generates tests that you can run from your terminal. It even has a codegen tool that records your clicks and generates test code automatically.
Running Tests Automatically With GitHub Actions
Once you have tests, run them automatically every time you push code. This catches broken code before it reaches your live app.
Ask your AI: “Can you set up a GitHub Actions workflow that runs my tests automatically every time I push code to my main branch? If any tests fail, the deployment should not proceed.”
Testing Your Most Critical Path First
Rather than trying to test everything, identify the one user action your app absolutely cannot afford to break. For a payment app, that is completing a purchase. For a project management tool, that is creating a new project. Write one test for that path first. Once it is passing and running automatically, add more tests incrementally.
The One Thing to Remember
Automated tests are code that checks your code still works. Start with integration tests on your most critical user flows using pytest or Jest. Add end-to-end tests with Playwright for journeys a user must complete. Set up GitHub Actions to run tests automatically on every push. Test your most important path first and add more incrementally.
Want your tested app deploying reliably to production? → Snapdock
New here? These might help: What is a staging environment? And do I actually need one? → I changed one thing and now my app is broken. How do I fix it? →