http://blogs.msdn.com/nikolait/archive/2008/06/04/fun-with-the-resourcereader.aspxAfter we released Pex recently, I came across a couple of interesting blog posts of people who tried out Pex, for example Ben Hall , Peter , and Stan . They all ran Pex on a small example. In this post, I want to run Pex on a more complicated piece ofen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/nikolait/archive/2008/06/04/fun-with-the-resourcereader.aspx#8574475Thu, 05 Jun 2008 06:05:17 GMT91d46819-8472-40ad-a661-2c78acb4018c:8574475Peter's Software House<p>Nikolai Tillmann has a great post on how to test the ResourceReader with Pex . I have also been playing</p> http://blogs.msdn.com/nikolait/archive/2008/06/04/fun-with-the-resourcereader.aspx#8837554Wed, 06 Aug 2008 17:26:28 GMT91d46819-8472-40ad-a661-2c78acb4018c:8837554Kathleen Dollard<p>Does PEX evaluate any managed code, specificlaly VB?</p> <p>The work you've done in evaluating the code is really cool. If this moves toward a real product (usable for commercial use, via CodePlex or included in a SKU) I'd love to see that work isolated as metadata that can be addressed in a less technology linked manner than a direct tie to generation. This this metadata (imagine XML for simplicity) could include a user specified tag per parameter set that indicated the anticipated exception, rather than just saying a set of exceptions are desired. </p> <p>Oen of the points of metadata access would also allow programmers to add their own parameter sets. It would seem that a single PEX generated test could run from the existing data-driven testing scenario.</p> <p>It would also seem that the constraint system - which is a very impressive approach - could be extended to access metadata concerning the CLR method parameters from a single evaluation. I care only what problems exist in my code, but I need the parameters to reflect all the things that can happen in the CLR stack. It seems silly for that to be constantly reevaulated, particularly through the relatively manual process described here.</p> <p>Cool stuff. I hope it moves toward a product. </p>