http://blogs.msdn.com/ploeh/archive/2008/10/06/naming-sut-test-variables.aspxIf you are a regular reader of this blog, you may have noticed that for the last couple of months, every test I've posted has shared some similarities; one of which is that I always name my SUT test variable sut . Here's a simple example: [ TestMethoden-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/ploeh/archive/2008/10/06/naming-sut-test-variables.aspx#8991177Wed, 08 Oct 2008 14:39:48 GMT91d46819-8472-40ad-a661-2c78acb4018c:8991177Jedidja<p>Interesting .. I never really thought about doing that. Going to give it a shot :)</p>http://blogs.msdn.com/ploeh/archive/2008/10/06/naming-sut-test-variables.aspx#8991586Wed, 08 Oct 2008 19:08:23 GMT91d46819-8472-40ad-a661-2c78acb4018c:8991586ploeh<p>Cool! At first it feels a little weird, so give it time to grow on you :)</p> http://blogs.msdn.com/ploeh/archive/2008/10/06/naming-sut-test-variables.aspx#9011060Wed, 22 Oct 2008 15:50:10 GMT91d46819-8472-40ad-a661-2c78acb4018c:9011060alex o.<p>Makes sense.</p> <p>In the past I have repeatedly gone through the exercise of renaming my test variables until I finally settle on a descriptive name.</p> <p>SUT might just cut it.</p>http://blogs.msdn.com/ploeh/archive/2008/10/06/naming-sut-test-variables.aspx#9065974Thu, 13 Nov 2008 14:52:19 GMT91d46819-8472-40ad-a661-2c78acb4018c:9065974ploeh blog<p>Writing good code is difficult. Unit tests are written as code, so a corollary to the first sentence</p> http://blogs.msdn.com/ploeh/archive/2008/10/06/naming-sut-test-variables.aspx#9131793Fri, 21 Nov 2008 15:56:22 GMT91d46819-8472-40ad-a661-2c78acb4018c:9131793ploeh blog<p>This is an installment in my Zero-Friction TDD series. Sometimes, you don't care about the return value</p>