Suggestion: Build a replacement for Microsoft Pex, fully integrated with the awesome Isolator framework.
We've been playing with Microsoft Pex automated unit test framework, and have been really blown away by the possibilities. It answers 2 things about your code:
1. Will my code crash? And if so, what method arguments will make it crash?
2. Does my code work as expected?
For #1, there is little-to-no developer effort - just run Pex, and it tells you where your code crashes and with what parameters, and optionally, generates unit tests to cover these cases.
For #2, you provide a parameterized unit test that describes the desired behavior, and Pex checks that behavior will hold under all parameters passed to it, in all states of the class under test.
This proves hugely useful for us: we can say whether a piece of code can crash, and also whether it is behaving properly, and Pex figures out all the parameters to make that happen.
However, Pex starts falling apart when used in the real world where you have dependencies, file system access, network and database access, etc. There, Pex provides a rather awkward "mock" framework/code generator called Moles. It sucks, and Isolator blows this away.
Enter TypeMock Isolator. You guys are a perfect fit for this. Build a piece of software that analyzes my code and tells me where it crashes, and with what inputs it crashes. Let me write a parameterized unit test that describes the desired behavior, and have your software tell me if it will behave as expected. Integrate this with Isolator to fake the dependencies. Life will be grand, and you'll have my dollars.
What do you think?