Small bugs, when released in the wild, will mate and multiply. 
Getting to full test coverage is cheaper than the long-term maintenance and support cost of the bugs you could be catching...
Show this thread
The purpose of unit tests isn't to verify the correctness of the new features you're checking in now. They're primarily a maintenance tool that enables you to make changes with confidence. They're meant to catch bugs in future unforeseen situations. Write them with that mindset.
-
-
That's why they used to be called regression tests.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This Tweet is unavailable.
-
YES, & moreso: Tests are written first to help you design your API, because you begin as a USER of the code instead of an implementer. Tests are written as specifications, to guide you in writing the code. Tests are guards to protect you when you’re refactoring.
End of conversation
-
-
-
Another good mindset I read about is that it forces you to write code that are testable, which encourages you to refactor and be more modular. For OOP, they also serve as example how to init and use classes.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I’ve been working on this: https://github.com/EricSchles/drifter_ml … it’s an ML testing framework. Granted it’s very naive at the moment, but I think one day it could get ML folks into the practice of testing and getting excited about it
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
And I know this sounds silly, but it's nevertheless very important for everything, especially maintenance: please, always comment (extensively!) your code!!!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.