🚀 TDD, Where Did It All Go Wrong (Ian Cooper)

What people said

globular-toast · 2024-04 · Strong recommendation

This the best talk I've ever seen about testing (Ian Cooper): [VIDEO] I see he's done a much more recent follow up, which I intend to watch: [LINK] Not sure if it contains new ideas. He says the unit is not "a class" but a module. It's up to you to decide what the module does (ie. what level of abstraction it's at). More importantly, he argues against mocking and essentially "unit testing" in most cases.

Read the original HN comment ↗

globular-toast · 2022-01 · Strong recommendation

Ian Cooper talked about this (and more) 5 years ago: [VIDEO] Well worth listening to this talk. It completely changed the way I did testing.

Read the original HN comment ↗

globular-toast · 2021-03 · Strong recommendation

> Firstly if the dependency isn't doing any io, you can test your code as a whole along with its dependency. No need to mock. This the thing. People have a tendency to overuse mocks. The point of automated testing (whether it's unit tests or something else), is to enable refactoring. That's really the only reason. Code that you don't touch doesn't suddenly change its behaviour one day. In a previous jobs the developers started to go crazy with mocking and it reached a kind of singularity where essentially if a function called anything, that thing was mocked. It definitely tests each function in complete isolation, but what's the point? It makes refactoring impossible, which is the entire point of the tests in the first place! This excellent talk completely changed the way I approached testing. Every developer who writes tests needs to watch this now! [VIDEO]

Read the original HN comment ↗