Yeah, seem he’s offering advice relevant for a very particular context: hundreds of developers, over many years, and (I’d guess) a dynamic language. Many valuable projects are not developed under those conditions, don’t need 100% coverage, can’t afford it, shouldn’t glorify it.
This might be the first time I disagree with him. But as someone who did automated testing for years- this I can't get behind. Tests are code and thoughtlessly accumulating tests can create huge burdens. Which ironically usually leads to people ignoring tests.https://twitter.com/fchollet/status/1273714126645161985 …
-
-
-
Oh yeah the dynamic language thing.... I think I'm in the minority and sound grumpy but I don't think a great selling point for the productivity of dynamic languages is that you can write code super fast....as long as you use a whole bunch of tests as a crutch for the language!
- Show replies
New conversation -
-
-
You have to be careful to test the underlying behavior that you really care about, not just some detail about how it's implemented now. Otherwise it'll be harder to refactor later because you'll break tests without breaking functionality
-
That's exactly it!
End of conversation
New conversation -
-
-
Totally agreed. Reminds me of this (excellent!) thread that matched my experience as wellhttps://twitter.com/sebaaltonen/status/1080073388570411009 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.