tag:blogger.com,1999:blog-38895959.post5306508476817949972..comments2009-06-17T12:07:00.151ZSimon Harthttp://www.blogger.com/profile/08526568682625258690noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-38895959.post-86494856472911740822009-06-17T12:07:00.151Z2009-06-17T12:07:00.151ZHi Daniel,<br /><br />Good point. Your point works to some degree. We use Rhino with MSTest - MSTest because it&#39;s integrated with TFS. Of course there are no mocking frameworks for the Compact Framework, sadly.<br />The example I posted could easy be tested with Rhino, MOQ or NMock etc but I think there is no substitue for testing device code on a actual device. If I were to test it on a desktop with a desktop mocking framework, then the test project would have to be a full .NET project. It&#39;s then a question of which classes can be tested on the desktop and the device and which ones can only be tested on the device. I find it easier to have a blanket rule to always test on the device against the CF.<br /><br />Of course testing would be a lot easier if using a mocking framework. The thing I&#39;m working on a at the moment could easily take advantage of desktop testing and mocking frameworks. It just means I&#39;d have to divide my test project up.<br /><br />Simon.Simon Harthttp://www.blogger.com/profile/08526568682625258690noreply@blogger.comtag:blogger.com,1999:blog-38895959.post-27156835736644061092009-06-16T20:52:40.384Z2009-06-16T20:52:40.384ZHi Simon<br />Sorry to bother you again ;) I usually tend to program hybrid code which then can be tested on the pc platform with NUnit and famous mocking frameworks like NMock2. I try to minimize the difference between the two platforms such that the general &quot;logic&quot; can be normally tested with NUnit and mocking frameworks. I hope you understand what I want to say because I&#39;m a bit tired...<br /><br />Greets DanielDaniel Marbachhttp://www.planetgeek.chnoreply@blogger.com