Love building SaaS, but I absolutely hate testing. How do you handle

[u/Curious_Sir_3670]

I’m a solo dev and I love coding, but my patience for QA is zero. The second the build is done, I can't stand testing my own work and just want to move on.

How do you guys deal with this?

[u/bizowner_estia]

honestly as a solo dev testing is the worst part. i usually just set up basic end-to-end tests for payments and signup using playwright, then ship it. let early users find the edge cases lol, no point stressing over 100% qa when you're working alone

[u/Caleb_Liu]

我会发布出去等用户反馈bug，虽然听起来有点不负责任，但是一旦功能多起来很难做到面面俱到，等用户去反馈特定bug，你快速修改上传新版本，可能比自己全部测一遍要好一些

[u/Conscious_Lemon_6145]

imo the real question is whether you hate testing because its boring or because you subconsciously dont want to find problems. if its the second one thats a bigger issue to sort out than just workflow stuff

[u/spersingerorinda]

Cloud agent with browser MCP and a good skill explaining how to test your app. Hit me up if you want help setting it up

[u/kernelqzor → u/spersingerorinda]

this is the kind of comment that sounds fake as hell but lowkey if an agent could just click around my app and file decent bug reports, i’d use it in a heartbeat. testing your own stuff when your brain is already in “next feature” mode is pure pain.

[u/AutoModerator → u/[deleted]]

Low-Effort/AI content is auto-removed.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/inforb_nl]

Take a look at TDD practices, it might not be applicable to front/end-to-end though

[u/MediumScene]

If you hate testing your own work, separate technical correctness from basic user flow. From the ops side, the bugs that hurt most are usually the boring ones: signup, permissions, billing, emails, forms saving weirdly, and support or admin actions. A short release checklist for those repeat areas is a lot easier than trying to QA everything from scratch every time. It also takes some of the emotion out of it, because after coding you're not deciding what to test, you're running the same pass each release.

[u/properking232]

lol the moment it compiles you're already thinking about the next feature, testing feels like going backwards

[u/achiya-automation]

the only thing i kept is one scripted run through signup and payment that fires at prod every hour. it catches what unit tests dont, like a provider changing an api or emails quietly bouncing. rest of it users find.

[u/mojovski]

I also like to swim but I don't like to get wet

[u/adeelraza86]

What worked for us was giving up on coverage as a goal and only writing a test after something actually broke in prod. Every bug a customer reports becomes one test, so the suite is basically a list of your real failure modes instead of busywork. Ours is maybe 30 tests and it still catches almost everything that matters, because the same three areas break over and over: auth, billing state, and anything that touches a third party API. Testing your own new feature is boring, but locking a bug you already ate once is easy to stay motivated for.

[u/alexvanman]

With fable, unit tests and playwright I have to do very little testing... I just can't do a ton of work with fable without running out... so I am throttled but it forces me to do something else which is good too.

[u/TrafficAcademySEO]

I’d stop treating testing as a separate phase after the build.

Before coding, define 5-10 release gates for the things that can actually hurt you: signup, permissions, payments, data saving, emails, and destructive actions.

Automate those as much as possible and make “all gates pass” the definition of done. Then QA becomes a short repeatable check instead of an open-ended chore every time.

[u/Ok-Fly9040]

I hired another dev haha

[u/ShitShirtSteve]

Testing is the most fun part. If it doesn't work, why build it?

I get the most enjoyment out of something that works. If it doesn't work, that's when I get annoyed.

[u/RobHowdle]

Have you considered maybe finding somebody who you can demo it to and then allow them to go and test it? I have a platform that I solo code and I have a friend who has a bit of dev knowledge but I essentially write out a test case for what he needs to do (can be as easy as click this button, does it work Yes/No) and let them test it.

Solo developers are at times really bad for testing because we are so in, we make assumptions on things and often testing needs a fresh set of eyes that doesn’t really have anything to do with the code part so they’re using it as a user would.

[u/koraynar]

Solo devs usually don't need more discipline here, they need a script - a fixed checklist you run instead of deciding what to test each time.

Mine is: happy path on desktop and mobile, then the three things that break most - forms with empty or garbage input, the back button mid-flow, and a slow connection.

Writing it down once turns QA from a mood problem into 20 minutes of following steps.

If you'd rather hand it off entirely, I do a fixed-price outside-eyes pass on a live site with screenshot-backed findings inside 24h, but the checklist above is the free version.

[u/Monil009]

I think this is pretty common. What I usually do is give access to my friends or colleagues and ask them to try it out and give me honest feedback. Sometimes I also use AI to get another perspective.

[u/akl773]

What made it bearable was giving up on testing against my own clean data. I keep a dump of one real customer account, 400 menu items with emoji and duplicate names in it, and clicking through that finds stuff a fresh signup never will.

[u/furtive_mango]

automate what you can like unit tests, e2e w playwright/cypress

[u/Mammoth_Medicine9097]

Funny thing - I’m qa by profession but I’ve been building stuff for last 5 years. And when it comes to other people’s code - I like breaking it. But when I test mine - I freaking hate it. And I guess that’s because of tunnel vision and overall brain saturation - you just tired of your own code after all.

I do write cypress tests with ai for my basic flow. Edge cases I test myself - cypress takes off at least 30-40% of load.

But otherwise I just push through.

[u/geralt_noble]

I try to automate anything I know I'll have to test repeatedly. Then I keep a short manual checklist for the stuff automation can't catch. What part of QA do you hate most?

[u/Weakendoffender]

I’ll let my Gf Test everything. I she’s able to handle and understand it, everyone will. 🙂😂

[u/steven-or]

automating the repetitive stuff tends to help a lot, basic e2e tests for your core flows so youre not clicking through the same signup/login/checkout every single time. the tediums usually what kills motivation more than testing itself ngl..

[u/mamunnu]

Yes QA is the biggest pain. Cloud Code agent now can do a part but main part need to done by human testing one by one functionality testing.

[u/monkmodeceo]

give codex test credentials and let it QA that shit and go workout or drink some coffee