Jason Bock demonstrated how to use Pex to identify defects in code. Pex can only investigate public methods. Integrates well with Visual Studio, enabling testing of a single method with a simple right-click.
You can optionally instrument framework classes if you wanted to investigate paths within the framework. But that can get pretty hairy X. can only analyze managed code.
Using CCI, he built AutoPex to enable Pex to run and focus specifically on changes from one build to another.
Jason also mentioned a number of the underlying technologies that are used in Pex, such as Z3 and Moles.
Jason said the latest version of Pex does not work with Visual Studio 2010 release candidate.
Twin Cities Code Camp 8
Saturday, April 10, 2010 from 8:00 AM – 5:00 PM (CT)