4 ms·
It was a single function that changed behavior after a refactoring. It did work where it did not need to, because the work was already done on the object. This
by jo909 9y ago
It was a single function that changed behavior after a refactoring. It did work where it did not need to, because the work was already done on the object. This is only hard if you don't test at all and can't already mock the object download/upload or don't have pure functions.
- jbergens 9y agoIn this case it might have helped, I didn't read the code, but in a more general case these kind of things are rarely found by unit tests. I still doubt that the triggering caused by the file change would have been found in a unit test.