3 ms·

That is quite fascinating. I do somewhat wonder if some of that can be lessened by using more "property based testing"[1]. Property based testing can be thought

by SEJeff 9y ago

That is quite fascinating. I do somewhat wonder if some of that can be lessened by using more "property based testing"[1]. Property based testing can be thought of writing tests that describe the functionality you are trying to cover. It then interpolates (not too unlike fuzzing actually) to come up with every way that might be non-compliant and then checks to ensure your hypothesis holds up. Amusingly enough, the most active python property based testing library is named hypothesis[2], which describes quite well how you write unit tests using it. [1] http://blog.jessitron.com/2013/04/property-based-testing-what-is-it.html http://blog.jessitron.com/2013/04/property-based-testing-wha... [2] https://hypothesis.readthedocs.io/en/latest/ https://hypothesis.readthedocs.io/en/latest/

nickpsecurity 9y ago
Here's one of those for C: https://github.com/silentbicycle/theft https://github.com/silentbicycle/theft Slides on automated tool below. They use "model-based testing" which is another phrase to get interesting search results. https://www.slideshare.net/dganesan11/ganesan-automated-testcasegenerationtutorial2012 https://www.slideshare.net/dganesan11/ganesan-automated-test... Also combinational testing which showed promise at catching in high 90's of defect percentage with test case minimization as a bonus. See summary and slides. http://csrc.nist.gov/groups/SNS/acts/index.html http://csrc.nist.gov/groups/SNS/acts/index.html