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

...Aaand, that's why we run the tests!

Better to fix it in a component/unit test than to lose the entire project

A successful test, identifying an flawed component design.




It's also worth pointing out that if your tests don't fail occasionally you may be over-engineering or being too cautious in your design and planning.


...or your test coverage is insufficient.


Also, a learning opportunity. If it had just worked, we would know less. Sometimes you have to blow up a few things to make progress--ask Elon.


>A successful test, identifying an flawed component design.

It could also be a flawed component. Just because the test failed doesn't mean the design is flawed.


true, thx (definitely a flawed writing component there)


Every inch of this is true, good tests are our success meter. /s




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

Search: