How to avoid brittle code

Re:How to avoid brittle code by mattnewton on Monday March 28, 2016 @11:32AM (#11374844)

This sounds hellish, I don't want red things flashing in my terminal while I'm in the middle of changing some function signatures; I know it's broken, I haven't gotten around to writing all the boilerplate to convince the tests I know about it yet though.

I'm with GP about integration tests.

[ Parent | on HN ]

Re:How to avoid brittle code by pekk on Monday March 28, 2016 @02:26PM (#11376210)

Growl doesn't flash red things in the terminal and nobody says you have to use Growl notifications if you don't like them, but this really has nothing to do with the usefulness of unit testing.

[ Parent | on HN ]

Re:How to avoid brittle code by glenjamin on Tuesday March 29, 2016 @07:44AM (#11380772)

Sometimes I'll hit save to confirm that the tests I expect to fail are doing so.

Sometimes I'll wait until I've finished changing all those function signatures until I hit save.

[ Parent | on HN ]