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

How would one unit-test an app like this, where you have to talk to an external database and over SMTP at a specific time of day? Seems like in a case like this thorough unit testing needs to be very extensive to catch a bug like this, yet it would have been worthwhile.


You would only need to unit test the programmer written ORM code against a seeded database to be sure you are getting just the data you expected.

You probably wont catch new issues with the ORM (which you should not be testing) but you will ensure you wont put this bug back into production.




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

Search: