tag:blogger.com,1999:blog-38895959.post5306508476817949972..comments2010-07-05T16:31:08.932ZSimon Harthttp://www.blogger.com/profile/08526568682625258690noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-38895959.post-13646424127283703092010-07-02T16:30:03.263Z2010-07-02T16:30:03.263ZI wasn&#39;t very clear but my point was your extension method is not specific to the compact framework and their is nothing preventing you from using it with in .net as a whole.<br /><br />My suggestion is that although you are using a cut down version of .net it doesn&#39;t mean you need to cripple your test library. Your blanket rule of testing against your device is all well and good but in this case you are making more work for yourself just to test that your code calls a method on an interface. Surly this is what integration tests are for.Bronumskihttp://www.blogger.com/profile/05091436116360365279noreply@blogger.comtag:blogger.com,1999:blog-38895959.post-21037109259867424832010-06-16T09:12:36.155Z2010-06-16T09:12:36.155ZHi Matt,<br /><br />Long time no speak!<br /><br />We&#39;ve just had another one, a little girl so we are very pleased!<br /><br />Going back to this, this is the whole point of mocking implementations out as this test is a unit test I&#39;m not interested in spanning multiple dependencies as it makes my test more complex and brittle. <br /><br />I shouldn&#39;t need to test the native implementation DbDataReader because i don&#39;t own it and it has already been tested. If this was an integration test, I wouldn&#39;t mock IDataReader.<br /><br />SimonSimon Harthttp://www.blogger.com/profile/08526568682625258690noreply@blogger.comtag:blogger.com,1999:blog-38895959.post-47764817439245649722010-06-15T11:16:42.799Z2010-06-15T11:16:42.799ZHi Simon,<br /><br />Valid point but I think in this case all you are doing is validating that your extension method is calling the correct method on the IDataRecord you&#39;ve not changed any of the native functionality.<br /><br />MattBronumskihttp://www.blogger.com/profile/05091436116360365279noreply@blogger.comtag: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