Code Contracts and Pex: Power Charge Your Assertions and Unit Tests
- Posted: May 28, 2010 at 5:01 AM
- 56,830 Views
- 2 Comments
By Nikolai Tillmann and Mike Barnett
Learn how Code Contracts provides a set of tools for design-by-contract programming and how Pex is an advanced unit-testing tool that uses automated program exploration to intelligently create unit tests with high code coverage.
See how they work together so that your code has fewer defects.
Learn about new features for Code Contracts including automatic documentation generation, call-site checking for components and reference assemblies for the .NET Framework and for Pex including a light-weight mocking framework, improved support for large code
bases, and more thorough test input generation.
Links:
PEX //
Code Contracts //
Mike Barnett //
Nikolai Tillmann // MDCC //
DPE DK
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
More entries in this blog
-
Using the new sensor and location API from…
-
Code Contracts and Pex: Power Charge Your…
-
Teaching programming language concepts with F#,…
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Near the end now and I really need to ask:
Witch one is nicer in your opinion ?
1. MDataTime.NowGet() = () => DateTime.Now;
2. Isolate.WhenCalled(()=> DareTime.Now()).WillReturn(DateTime.Now);
And you know what's great, WillReturn can have a delegate also, but it does not have too all the time.
> Witch one is nicer in your opinion ?
Let's say that both are not as good as they could be. Language/CLR support would be the ultimate solution.
ps: 1. will result in a stackoverflow since the delegate will recursively call itself. Not sure about 2.
Remove this comment
Remove this thread
close