3 ms·
Do you think the test is written and the bug left in? What a weird take. And then, you write the test so that future changes (small or big) that causes regress
by 7bit 2y ago
Do you think the test is written and the bug left in? What a weird take.
And then, you write the test so that future changes (small or big) that causes regressions get noticed before the regression is put into production again. Especially in complex systems, you can define the end result and test if all your cases are covered. You do this anyway manually, so why not just write a test instead?
- whatever1 2y agoThe time that you spent to write a test is the time you would have spent in finding another bug in the code. Your time is finite. Bugs are not.