﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Dim Blog As New ThoughtStream(me) commented on Guidelines to using Interaction Based Testing</title><description>We have been doing a Lunch-N-Learn session every Wednesday for a few weeks now. Today's session was presented...
</description><link>http://ayende.com/2288/guidelines-to-using-interaction-based-testing#comment3</link><guid>http://ayende.com/2288/guidelines-to-using-interaction-based-testing#comment3</guid><pubDate>Thu, 05 Apr 2007 14:20:05 GMT</pubDate></item><item><title>Christopher Bennage commented on Guidelines to using Interaction Based Testing</title><description>That's very useful.  Though perhaps we could call them something else? Like, MockForData Objects, and MockForExpectation Objects.  :- )
  
(Fake and Mock overloaded threw me off a bit, but I am still on my first cup of coffee ...)
</description><link>http://ayende.com/2288/guidelines-to-using-interaction-based-testing#comment2</link><guid>http://ayende.com/2288/guidelines-to-using-interaction-based-testing#comment2</guid><pubDate>Thu, 05 Apr 2007 13:57:03 GMT</pubDate></item><item><title>Jeroen van Menen commented on Guidelines to using Interaction Based Testing</title><description>Good advice, thanks. I entered this (same) problem when I was changing some of the WatiN tests. Didn't know about SetupResult, but will look into it.
  
</description><link>http://ayende.com/2288/guidelines-to-using-interaction-based-testing#comment1</link><guid>http://ayende.com/2288/guidelines-to-using-interaction-based-testing#comment1</guid><pubDate>Thu, 05 Apr 2007 07:53:26 GMT</pubDate></item></channel></rss>