I'm reaaaaaaly not a fan of code contracts for this type of work. It makes much more sense in the context of customer-facing, line-of-business & enterprise apps.
The command-line tools (category A) are pretty darned straight forward; Perhaps we could use real-world samples for test cases, but without the need constantly sync them with the original code. (ie grab the zlib source and have the tests unpack it, run it thru the gauntlet, and validate the results). Garrett Serack | Open Source Software Developer | Microsoft Corporation I don't make the software you use; I make the software you use better on Windows. From: Jonathan Ben-Joseph [mailto:[email protected]] Sent: Wednesday, April 21, 2010 10:48 AM To: Ritchie Annand Cc: Garrett Serack; [email protected] Subject: Re: [Coapp-developers] Thinking abotu testing CoApp's tools. Well, I believe we could do some unit tests on the individual classes. It might also be worth doing some functional tests on the commands themselves. Another thing worth looking at (although perhaps not directly related to testing) is code contracts (http://msdn.microsoft.com/en-us/devlabs/dd491992.aspx). Code contracts allow for some additional run-time checking of correctness. Jonathan Ben-Joseph
_______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
