4 ms·
...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 comp
by toss1 9y ago
...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.
- mejari 9y ago>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.
- toss1 9y agotrue, thx (definitely a flawed writing component there)
- TomK32 9y agoEvery inch of this is true, good tests are our success meter. /s
- mattnewport 9y agoIt'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.
- Sharlin 9y ago...or your test coverage is insufficient.
- imglorp 9y agoAlso, 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.