http://dotnet-forum.de/blogs/rainerhilmer/archive/2009/10/30/testing-a-dismantled-linq-expression.aspxIn my last Blog post I complained about my testability woes with LINQ expressions. Here are the test methods I used to track down the bug. Oh and I violated the coding conventions which tell us to use the “Should…” naming strategy for test methods. ICommunityServer 2007.1 (Debug Build: 20917.1142)http://dotnet-forum.de/blogs/rainerhilmer/archive/2009/10/30/testing-a-dismantled-linq-expression.aspx#32220Thu, 18 Feb 2010 12:16:13 GMT6dcdb6ae-26a7-4704-ae8b-cbd278e59bdf:32220Rainer Hilmers Developer-Blog<p>Oft wird mir etwas unwohl wenn ich eine Lambda expression sehe. Lange Zeit wu&#223;te ich nur vage warum &#252;berhaupt</p> <img src="http://dotnet-forum.de/aggbug.aspx?PostID=32220" width="1" height="1">http://dotnet-forum.de/blogs/rainerhilmer/archive/2009/10/30/testing-a-dismantled-linq-expression.aspx#7004Sat, 31 Oct 2009 22:30:18 GMT6dcdb6ae-26a7-4704-ae8b-cbd278e59bdf:7004Rainer Hilmers Developer-Blog<p>This is part 3 of my Blog posts about LINQ testability issues. You know what this is all about when you</p> <img src="http://dotnet-forum.de/aggbug.aspx?PostID=7004" width="1" height="1">