4 ms·
A good interface is testable, this is how you build up reliable abstractions to solve higher level problems. The devs on my team that take shortcuts here waste
by jessekv 2y ago
A good interface is testable, this is how you build up reliable abstractions to solve higher level problems. The devs on my team that take shortcuts here waste more time in the end.
There is no cost trade-off.
- miningape 2y agoIn most cases especially for important code paths I agree. There is a case where I think it is justifiable to not write a single test: Startups. Specifically pre-seed & seed round funded I think are allowed to skip the majority of tests - however critical paths, especially those that are important to customers (i.e. transactions) must be tested. By the time you have built out that mvp and have a few customers then you should transition to writing more tests. And as the number of engineers, scope, or complexity grows you need to add tests.
- CamperBob2 2y agoIt's testable right up until the point where it's asynchronously interactive. Would unit tests have avoided the Therac-25 incident?