http://blogs.msdn.com/mohamedg/archive/2009/05/14/test-patterns.aspxJust like design patterns, the use of test patterns will make your life easier. A lot of the common testing methods can be reused. Along with the benefits of reuse, using patterns makes it easier to explain to others what you are going to do in a worden-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/mohamedg/archive/2009/05/14/test-patterns.aspx#9614374Thu, 14 May 2009 09:07:30 GMT91d46819-8472-40ad-a661-2c78acb4018c:9614374Test Patterns | Microsoft Share Point<p>PingBack from <a rel="nofollow" target="_new" href="http://microsoft-sharepoint.simplynetdev.com/test-patterns/">http://microsoft-sharepoint.simplynetdev.com/test-patterns/</a></p> http://blogs.msdn.com/mohamedg/archive/2009/05/14/test-patterns.aspx#9811708Wed, 01 Jul 2009 22:13:54 GMT91d46819-8472-40ad-a661-2c78acb4018c:9811708Hatem Nassrat<p>I agree that if a problem has already been solved, then one should use the technique that has been proven to work. However, today we see many people trying to use a patterns &nbsp;(mainly design patterns) where they do not fit. For example, some senior Java programmers (collegues) will not think your software is good enough unless you employ every single pattern whether or not it makes sense. I dislike that way of thinking, where people think of the pattern before the problem, we should not put the horse behind the carriage, but on the other hand, look at the problem and try to find a sollution which best fits the problem. Slightly off topic here :), but when looking at test patterns many people use the one hammer fits all approach. Many projects rely heavily on unit testing and forget other important testing strategies, or even try to think of what fits best.</p> <p>Nice post Geish!</p>