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

Just like if you wear a seatbelt all your life, but never have an accident, what a waste of effort. Not to mention $$$ spent on car insurance.

Programmers should peer into their crystal balls and predict which code is going to need to be maintained in ways that will break it and only write regression tests for that. For all the rest, just poke at it manually in your REPL and debugger and call it tested.

You heard it here.



Yes, I'll write a test for something that I know from experience is likely to give me trouble later on with regression problems

Writing a test when you find a bug and then fixing the bug is also quite handy sometimes

And I'll write tests upfront when there's well defined outcomes and I know the code is going to be tricky

But I'm not going to write tests for dumb stuff that I know wont break




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

Search: