How do you test your SaaS product's UI? Share your favorite tools and strategies
Hey Indie Hackers,
I'm curious about how you tackle end‑to‑end UI testing for your web apps, SaaS products or online stores. What tools or frameworks do you rely on to make sure your user flows work smoothly across browsers and devices? Do you write tests yourself, use record‑and‑playback tools, or something else entirely?
I'd love to hear about the pain points you've encountered and any tips or best practices you've discovered. Sharing your experiences could help others (including me) improve our testing workflows.
Looking forward to learning from the community!
Trending on Indie Hackers
The biggest pain point I've seen is test maintenance becoming a second job. Record-and-playback tools generate tests fast, but they break constantly when the UI changes - and indie hackers ship UI changes constantly.
My approach: test the critical path ruthlessly, ignore the rest. For most SaaS products, that's signup → core value action → payment. If those three flows work, you're probably fine.
Playwright has been solid for this. The selector engine is smart enough to survive minor UI shuffles, and the codegen tool gets you started without writing everything from scratch.
The real trick is knowing what NOT to test. Every test you write is a test you have to maintain. For early-stage products, I'd rather ship faster and handle edge cases manually than build a comprehensive test suite that slows everything down.
What's your current setup? Are you testing anything right now, or starting from zero?
makes sense! thanks for sharing. We use Playwright-based browser automation + LLMs currently.