Unit tests are pointless. Integration tests are hard. Clicky tests are king.
You write a piece of code, and you know it works. You just wrote it. You just ran it. You just saw it do everything you thought to try. Any unit or integration tests would have confirmed this.
Your PM gets your code and tries it out. He or she finds a bunch of things you forgot. Bits of the spec that you missed, nuances in edge cases you didn't think of, strange things even the PM didn't think of.
The designer finds a bunch of crap that should've been obvious, but you're not a designer, so you didn't think it was obvious.
You get back to your code. Any tests you would have written wouldn't have caught any of this stuff. You didn't think of it, so you wouldn't have written a test. Even if you did assume you aren't perfect and needed tests. You don't need tests.
You fix the things. You test the things. Sometimes, you test something twice because you notice fixing it broke something else. Keeping all the balls in the air is annoying, but totally doable. You don't need tests.
Your PM says ??. Your designer says gorgeous.
Your QA team gets the code. You tell them which manual test cases to do. It takes them half a day, but your code is good. You don't need tests.
Your user gets your code. It breaks. They did a thing that you didn't think to try, your PM didn't think was related, and nobody told QA to try.
Your user is nice enough to file a Usersnap report.
"Nonsense", you say, "one in a million case. I can't reproduce that."
Five more users find the bug. You notice a pattern. Your PM says this is now a production issue and should be fixed immediately.
You drop everything you were doing. You fix the thing. You test the thing. Sometimes you test something twice because you notice fixing it broke something else. Keeping all the balls in the air is annoying, but totally doable. You don't need tests.
Your PM says ??. You add a line item to QA's plate. It takes them half a day to test everything. QA says ??. Your code goes to production.
Your users say nothing. Quiet users are good users. You don't need tests.
Six months pass.
It is time to refactor your code. You would kill for some tests.
Here's how it works 👇
And get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️