I'm not sure what to do with that idea, but that's actually the core of why I posted this. Any other hackers out there excited by this idea?
I'm not sure what to do with that idea, but that's actually the core of why I posted this. Any other hackers out there excited by this idea?
Unit tests are kind of handy if you've got some sort of "fencepost" style error where you need to figure out a piece of logic that was overlooked. But that's about it.
This sort of testing would way more relevant, because it's a way of focusing on "what (data) do we 'well' right now"?
I'm thinking that such sort of systems might be useful as a basis for performance or concurrency testing for example.
statistical bug isolation: http://pages.cs.wisc.edu/~liblit/pldi-2005/
CHESS - automated finding of concurrency bugs: http://research.microsoft.com/en-us/projects/chess/
you could start from there and traverse thru related work