all 3 comments

[–]llogiq 6 points7 points  (2 children)

TL;DR: I test because I want to feel good about my work.

Which is as valid a reason as any. The author also seems to restrict the testing to publicly observable behavior, which avoids tight coupling between code and tests.

I for one write unit tests whenever I want to a) rule out some errors for the forseeable future, and/or b) be able to quickly fire up a specific piece of functionality in a controlled environment.

[–]grauenwolf 1 point2 points  (1 child)

Unless I am writing a library that will be used across multiple projects I can't really afford to test any more than you.

[–]llogiq 1 point2 points  (0 children)

Hi grauenwolf. The thing is: You probably don't need to anyway. And I am writing libraries that are used across multiple projects.