Flex Your Pex!

May 9, 2009 · 1 min read

PexLogo_thumb

I recently took the Pex framework for a test drive and spent a few weeks off and on trying to make sense of it all.  Lots of promise with this framework, and I bought into it all – I really like to test my code, but writing code to cause a framework to generate the tests sounded cool.  Yet another shiny thing in the world of testing – I know.

I first saw this running at a PnP Summit last November and just recently got to put it in play, and while I was waiting a few new builds dropped that made things a bit easier.

I wrote a really nice document, for my own shop which makes sense if you knew the project I was working on.  I’m going to decompose the document and publish that in chunks that make sense.

I barely tapped the full capacity of this tool, but to give you an idea of what how well it work, here are a few stats I can share.

I was working with 17 facade classes with a total of 750 Blocks (per Visual Studio Code Coverage) and covered 92% of them.  Yes, it took a while, and there was slight curve but there’s a ton of documentation to help out.  This is well worth investigating, you won’t be sorry.

Check back for the installments.

This article is part of the GWB Archives. Original Author: onefloridacoder

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.