Testing
Post #6205, on Aug 28, 2024 in TG
The Unofficial QA Team: Testing in Production
Description
A screenshot of a chat conversation, likely from Discord, between two users, 'Matt' and 'kitty.' Matt starts the conversation with the notoriously bad advice, 'just test in prod.' Kitty sarcastically agrees, replying, 'yeah we have a team of testers,' and then adds the punchline, 'they're called users.' This meme captures a cynical but common joke in the software development world, where inadequate testing or pressure to release quickly leads to bugs being discovered by end-users in the live production environment. It highlights a disregard for proper quality assurance (QA) processes and the potential consequences of shipping untested code
Related Memes
Use J and K for navigation
Comments
16Comment deleted
We don't have a staging environment, we have 'prod-staging,' which is just prod on a Tuesday. If nothing's on fire by Wednesday, we call it a successful release
We skipped staging altogether - now every login is a unit test, every outage is an integration test, and the post-mortem doubles as the release notes
After 20 years in tech, I've learned there are only two types of companies: those who admit they test in production, and those who call it 'progressive rollout with real-time user acceptance validation' in their SOC 2 compliance docs
Ah yes, the classic 'continuous delivery to production' strategy where your monitoring dashboard doubles as a bug tracker and your user base provides real-time integration testing at scale. It's not a lack of QA process - it's just extremely distributed testing with highly motivated stakeholders who have a vested interest in finding edge cases. Some call it reckless; we call it 'production-driven development' with a feedback loop measured in angry support tickets per second
“Test in prod” is progressive delivery without feature flags, observability, or a functioning error budget - aka a live A/B test where B stands for blame
Prod testing: infinite parallel canaries, zero flakiness tolerance, and logs full of unredacted user sob stories
Users-as-QA is a 100% canary with zero metrics, no kill switch, and your entire error budget footing the bill
btw, its okay if you test on 0.01% of all users first and slowly expand if no errors detected. Comment deleted
Those poor 0.01% users Comment deleted
Who're paying premium for the new features on top of that! xD Comment deleted
CrowdStrike: hold my beer! Comment deleted
that's called involuntary beta program Comment deleted
deploy on friday test with all users turn off your phone Comment deleted
ssh root@prod git pull Comment deleted
lemme send that to the boss xDDD Comment deleted
Testing? What is that? We are P-R-O-F-E-S-S-I-O-N-A-L-S. We run what we write Comment deleted