http://blog.excastle.com/2008/06/09/teched-2008-notes-lessons-learned-in-programmer-unit-testing/ Life, .NET, and Cats Fri, 21 Nov 2008 04:49:11 +0000 http://wordpress.org/?v=2.5 http://blog.excastle.com/2008/06/09/teched-2008-notes-lessons-learned-in-programmer-unit-testing/#comment-21730 Jim Fri, 13 Jun 2008 21:19:15 +0000 http://blog.excastle.com/?p=2550#comment-21730 Very interesting; thanks. I am not following on how mocking is bad for state testing. Mocks are just a simulation of other classes that you substitute for control and performance. My thought is that my test actions move the object to a state or action that I test. I’m missing the point on the bad side of the statement. I may not grasp "state testing". Can you elaborate just a bit. Thx. Very interesting; thanks. I am not following on how mocking is bad for state testing. Mocks are just a simulation of other classes that you substitute for control and performance. My thought is that my test actions move the object to a state or action that I test. I’m missing the point on the bad side of the statement. I may not grasp “state testing”. Can you elaborate just a bit. Thx.

]]> http://blog.excastle.com/2008/06/09/teched-2008-notes-lessons-learned-in-programmer-unit-testing/#comment-21599 Joe White’s Blog » Blog Archive » TechEd 2008 notes: How not to write a unit test Fri, 13 Jun 2008 04:48:55 +0000 http://blog.excastle.com/?p=2550#comment-21599 [...] Suggestion: don’t call the method directly from Assert.AreEqual(...). Introduce a temp variable instead. (This relates back to the 3A test pattern.) [...] […] Suggestion: don’t call the method directly from Assert.AreEqual(…). Introduce a temp variable instead. (This relates back to the 3A test pattern.) […]

]]>