3 ms·
"Unit tests are [...] proof that the work that you just did is correct and you can move on." Unit tests only can proof your software to be buggy. Even for the
by Someone 10y ago
"Unit tests are [...] proof that the work that you just did is correct and you can move on."
Unit tests only can proof your software to be buggy. Even for the extremely simple "two, a function that, given no arguments, returns the number 2", your unit test can't verify that to be _always_ true. It may fail to return on Tuesdays (https://bugs.launchpad.net/ubuntu/+source/file/+bug/248619 https://bugs.launchpad.net/ubuntu/+source/file/+bug/248619), internally use a web service that doesn't work on leap days (http://www.wired.com/insights/2012/02/leap-day-azure-outage/ http://www.wired.com/insights/2012/02/leap-day-azure-outage/), other calls may overwrite the 'constant' it returns (http://programmers.stackexchange.com/questions/254799/ever-change-the-value-of-4-how-did-this-come-into-hayes-thomas-quiz http://programmers.stackexchange.com/questions/254799/ever-c...), etc.
- mdpopescu 10y agoYou can verify it to always be true as long as the dependencies (which you've mocked) hold. If they don't... if that's a possibility then you might need some error recovery somewhere, not necessarily in this particular unit.
- sangnoir 10y ago> Even for the extremely simple "two, a function that, given no arguments, returns the number 2", your unit test can't verify that to be _always_ true That is true, I don't think anyone argues against that point. What unit tests do, is verify that under the code works under specific conditions (as defined in the test's set up). When unit tests fail under those specific conditions, then you know there is a problem. Another thing I like about unit tests is that it is much easier (and faster) to test different combinations of conditions
- majewsky 10y agoIn functional programming languages, the type of "two" would indicate whether it has side effects. If not, then "two() == 2" is conclusive proof.