3 ms·
Surprised by the responses here. Unit tests and smoke/E2E are like peanut butter and jelly, they're better together. And yeah they're expensive to build but it
by tired_and_awake 3y ago
Surprised by the responses here.
Unit tests and smoke/E2E are like peanut butter and jelly, they're better together. And yeah they're expensive to build but it's almost always cheaper than deploying crap and hurting your customers.
Why all the drama?
- drpossum 3y agoI assume they're different from me and write bug-free code that never needs to be refactored the first time.
- bitzun 3y agoThe drama is mostly because lots of people don't like writing tests, and lots of folks at one point or another have seen unit tests that are questionably valuable or past the point of diminishing returns I think of tests that require a bunch of scaffolding to mock out any meaningful logic in order to test a single, simple if statement that invokes some other business logic that is already meaningfully tested on its own. At that point, it's easy to say "Wow, a couple of E2E tests would have caught the whole shebang!" Maybe I've just been burned by how easily one (read: I) can accidentally write pointless unit tests in Python. I think the unit testing "debate" when it comes up tends to be very handwavey, like this article (which I still think is thoughtful.)