The User-Driven Testing Strategy
Description
A meme featuring text at the top and an image below. The top text, in a simple black font, reads: 'Interviewer: "But how can the testers keep up with all these constant changes?"'. The image below shows a person in a dark room, illuminated by a computer monitor. This person, labeled 'VIBE CODER', wears a bucket hat, large futuristic sunglasses, and headphones, looking intently at the screen. Overlaid text on the right side of the image provides the coder's response: 'TESTERS? YOU MEAN USERS?'. The meme satirizes a development culture that forgoes a formal quality assurance (QA) or testing phase, instead relying on end-users to discover bugs in the live production environment. This 'testing in production' approach is often associated with a 'move fast and break things' mentality, prioritizing development speed over stability, a mindset sometimes found in startups or projects where rapid iteration is valued above all else
Comments
16Comment deleted
We have a robust testing environment; we call it 'production'. Our users are the most dedicated QA team, and their bug reports are... passionately detailed
Our QA strategy? Ship behind a feature flag, let 1 % of users consume the new code, watch the error budget vaporize in Grafana, then flip it to 100 % and call it “tests passed in production.”
After 20 years in the industry, you realize the most honest architecture diagram is just a straight line from git push to production, with a tiny dotted box labeled 'hope' where QA used to be
Ah yes, the classic 'continuous delivery to production' strategy where your monitoring dashboard is actually user support tickets, and your test coverage is measured in angry tweets. When the interviewer asks about your CI/CD pipeline, they don't realize the 'CD' stands for 'Customers Debug' - because why maintain a QA environment when you have millions of unpaid beta testers with real data? It's not a bug, it's an unannounced A/B test with a 50% error rate
Testers? We shifted so far left it wrapped into prod - feature flags, canaries, and an error budget; marketing calls it “early access,” users call it Tuesday
The ultimate SRE optimization: offload QA to a distributed user cluster - infinite scale, zero headcount, and they fund your infra bills
Our QA plan is feature flags, 1% canaries, and a generous error budget - when it backfires, marketing rebrands it as “open beta” and calls it customer engagement
100 commits in 2 days Comment deleted
Me but fighting with CI Comment deleted
Vibe coders: testing? Don't you mean pushing to prod? Comment deleted
I've tried adding tests to some open source projects before only to be told "we don't need tests, if there was a bug our users would tell us" I immediately back off the project when that happens, and remove my local deployments. Comment deleted
Your pfps made me worried Comment deleted
Bro is morse code Comment deleted
Haha I have a bot that changes it to sleeping when I'm asleep, but it doesn't always clean up the old ones Edit: tidied up the duplicates now Comment deleted
Wait, is that real ?! He's now one of us?🤯🤯🤯 Comment deleted
Yall don’t even understand. We used to live edit PHP in prod. Testing? Who the fuck needs that? Comment deleted