Chuck Esterbrook wrote:
One is Pex which analyzes your code to determine boundary conditions
which it then uses to try to break your unit tests by passing in
parameter values around those conditions.
FWIW, this is a pretty old idea. Maybe Pex is doing something cool, or
doing it in new ways, or whatever, but the general concept of looking at
(for example) numeric constants and driving tests through the code that
get near and across those constants is old.
Maybe the research is how to keep it from turning into an N! explosion
to find the inputs that drive it that way. That was always the problem.
Thanks for the links!
--
Darren New / San Diego, CA, USA (PST)
--
KPLUG-LPSG@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
