Changing Bits: Your test cases should sometimes fail!

Changing Bits: Your test cases should sometimes fail!

Your test cases should sometimes fail! I'm an avid subscriber of the delightful weekly (sometimes) Python-URL! email, highlighting the past week's interesting discussions across the numerous Python lists . Each summary starts with the best quote from the week; here's last week's quote : "So far as I know, that actually just means that the test suite is insufficient." - Peter Seebach, when an application passes all its tests. I wholeheartedly agree: if your build always passes its tests, that means your tests are not tough enough! Ideally the tests should stay ahead of the software, constantly pulling you forwards to improve its quality. If the tests keep passing, write new ones that fail! Or make existing ones evil-er. You'll be glad to know that Lucene/Solr's tests do sometimes fail, as you can see in the Randomized testing Our test infrastructure has gotten much better, just over the past 6 months or so, through heavy use of randomization.

Read full article from Changing Bits: Your test cases should sometimes fail!