3 ms·
> Automated testing takes less time Hmm, this has not been my experience, but I spend a lot of time in the UI. Writing UI tests is a massive pain, the functio
by qudat 4y ago
> Automated testing takes less time
Hmm, this has not been my experience, but I spend a lot of time in the UI. Writing UI tests is a massive pain, the functions are impure, naturally deal with side-effects, and involve robo-interacting with a fake browser. The amount of code required to simply scaffold a fake browser that works reasonably is a monumental feat and that's before you start writing a single test.
Further, it's not enough to measure how long it takes to write a test but also to maintain them. That's the time creep that can be absolutely brutal.
- treis 4y agoWe do a lot of mock 15 different things so that you can unit test this one thing. I too think it's a drag because it tends to ossify things. Not only do I have to change the code I have to change all the unit tests and mocks. And it just doesn't seem to catch a lot of stuff. Or at least a lot of bugs slip through I wish we had spent that time on better anomaly detection and defensive coding and stuff like blue green deployments. Users are the best testers and it's not really a big deal if 2% of your users see a bug for 10 minutes. Maybe different if people will die or if money will be lost. But for general business or consumer stuff I think it's fine.
- hbrn 4y ago> Users are the best testers and it's not really a big deal if 2% of your users see a bug for 10 minutes. This is the product engineer mindset. Your job is to deliver value, and you use tools that deem appropriate and most efficient. But most engineers tend to be disconnected from value (both by their own choice, and by organization structure). When you don't know what the value of what you're producing is, you start clinging to other signals, most of which are actually noise.