Comments for Agile methodology, .NET technology

Comment on Easy to fix issue between NServiceBus and Code Contracts by Steve Degosserie

Steve Degosserie — Fri, 18 Jun 2010 07:16:40 +0000

So, how's your experience with NServiceBus so far ? You should blog about it

Comment on Code Contracts: Static checking doesn't work on Attributes by Roy

Roy — Mon, 10 May 2010 14:10:29 +0000

I think code contracts should be unit-tested, just like any other public part of the code. After all, contracts, by their very nature, describe behavior/conditions the code must adhere to. So it only makes sense to test whether those tests are indeed in-place and whether they work.

Think of it as regression testing: who is to say that a code contract present today may not be (accidentally?) removed?

A third argument would be that not only code contracts, but also unit tests serve as documentation. Therefore, it is extra important that all conditions/behaviors inherent in the code are tested properly.

A fourth argument would be that you cannot have 100% coverage if you don't unit-test contracts.

I hope this helps,

Roy

Comment on Code Contracts: Static checking doesn't work on Attributes by Mr. Bungle

Mr. Bungle — Sun, 09 May 2010 04:35:53 +0000

Another great post on code contracts, keep them coming Roy. I'm interested in your opinion on the need to verify code contract behaviour in unit tests (i.e. the need for PriorityQueue_EnqueueNull_ThrowsArgumentNullException() in your "Code Contracts By Example" post). It seems many people believe this sort of test is unnecessary / redundant (e.g. the answers on this Stackoverflow question). Consider the case where you have two implementations of IPropertyQueue, would you add such tests to both or just one of the classes?

Comment on First Impressions: Scrum for Team System 3.0.3698.00 with Team Foundation Server 2010 by DotNetShoutout

DotNetShoutout — Wed, 14 Apr 2010 21:48:49 +0000

First Impressions: Scrum for Team System 3.0.3698.00 with Team Foundation Server 2010…

Thank you for submitting this cool story — Trackback from DotNetShoutout…

[WORDPRESS HASHCASH] The comment's server IP (206.72.113.4) doesn't match the comment's URL host IP (206.72.113.143) and so is spam.

Comment on Code Contract Coding Conventions by DotNetShoutout

DotNetShoutout — Wed, 17 Feb 2010 20:36:21 +0000

Code Contract Coding Conventions…

Thank you for submitting this cool story — Trackback from DotNetShoutout…

[WORDPRESS HASHCASH] The comment's server IP (206.72.113.4) doesn't match the comment's URL host IP (206.72.113.143) and so is spam.

Comment on Code Contracts By Example by Roy Dictus

Roy Dictus — Thu, 04 Feb 2010 15:52:14 +0000

Hi guys, thanks for the input.

Hey Steph, .NET 3.5 is good but 4.0 is better

Yes, I'm using Pex, and will certainly write about it soon. I haven't worked with Chess yet, but then again, I'm not really writing any parallel code at the moment.

Comment on Code Contracts By Example by Steve Degosserie

Steve Degosserie — Wed, 03 Feb 2010 13:02:19 +0000

Hey Roy, very nice posts. Did you have a look at Pex (http://msdn.microsoft.com/en-us/devlabs/cc950525.aspx) & CHESS (http://msdn.microsoft.com/en-us/devlabs/cc950526.aspx), they're super interesting as well

Comment on Code Contracts By Example by Steph

Steph — Wed, 03 Feb 2010 10:48:33 +0000

Nice post ! except for the fact i'm old school

Comment on Quality Assurance Tool: Code Contracts by Code Contracts By Example

Code Contracts By Example — Wed, 03 Feb 2010 00:14:27 +0000

[…] I blogged about Code Contracts as a tool to help you specify and verify code behavior. Today let's […]

Comment on Hello world! by Gabriel Lozano-Moran

Gabriel Lozano-Moran — Fri, 29 Jan 2010 17:46:28 +0000

Welcome back to the blogosphere!