Hacker News new | past | comments | ask | show | jobs | submit login

While I agree, integration tests can be pretty costly in term of time to set up.

In the small places I have worked, it been acceptable to have a few bugs, and the applications were completely or partially used by internal users, so maybe 40 -50 people who can put up with a bug here or there and report issues personally.




I find that integration tests tend to have a much higher set up cost (especially if you are serious about test isolation), but that cost is amortized over the lifetime of the project because the code is much more reusable.

Unit tests are less expensive to set up on a per test basis but the code is less reusable and the ongoing maintenance tends to be higher.


Probably, provided that your system is evolving too quickly - that can often be a problem.




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

Search: