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

> My preference is always to actually test parts in as close as possible to the real state, avoiding mocks unless they're necessary. The more "fake" the system is, the less it tells you about how your software actually works.

I've heard this before, but never actually had that problem with fakes in practise. Where can I read more about it?



Have a production outage. See the code in question is 100% tested. Scratch head a bit. Vow to fake less next time.


Supposedly the software problems with the Starliner spacecraft were also caused by extensive unit testing under test harnesses without integration testing, as a visible example that reached the news.




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

Search: