>The basic premise of TDD, for those unaware, is that one first writes a unit test that verifies the expected behavior for some function
No, not "some function". The tests should mimic the expected behavior of a scenario using the app.
Only if the function is acting as a close approximation of the app itself do you get any benefits out of TDDing it.
90% of the shitty tests I've ever seen in my life have been written as a result of a mid level developer thinking that the test should "surround some function" (they dont seem to think it matters which ones you pick) rather than reflecting an actual user story.
MoreQARespect•1h ago
No, not "some function". The tests should mimic the expected behavior of a scenario using the app.
Only if the function is acting as a close approximation of the app itself do you get any benefits out of TDDing it.
90% of the shitty tests I've ever seen in my life have been written as a result of a mid level developer thinking that the test should "surround some function" (they dont seem to think it matters which ones you pick) rather than reflecting an actual user story.
This blog is a reflection of that same attitude.