Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> aim for good test coverage

From the beginning? Not. That's completely counterproductive.

The first thing you have to do is be sure that you are testing the correct thing. Only after it you write your tests down.

Specs come before tests, and on most problems you will need to write a lot of code before your get the specs down.



Is the correct thing that doesn’t work correctly under some conditions always the correct thing. Users are polite and will not tell you about the annoying whack a mole bugs that keep cropping up...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: