<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>andrewmccall.com - Latest Comments in Some thoughts on unit tests</title><link>http://andrewmccall.disqus.com/</link><description></description><atom:link href="https://andrewmccall.disqus.com/some_thoughts_on_unit_tests/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 16 Oct 2009 14:33:24 -0000</lastBuildDate><item><title>Re: Some thoughts on unit tests</title><link>http://andrewmccall.com/2009/07/some-thoughts-on-unit-tests/#comment-20211372</link><description>&lt;p&gt;Andrew:  You mentioned making up mock objects for hbase.  Can I see what you did?  Trying to make the hbase tests run faster overall...  Thanks.  St.Ack&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">stack</dc:creator><pubDate>Fri, 16 Oct 2009 14:33:24 -0000</pubDate></item><item><title>Re: Some thoughts on unit tests</title><link>http://andrewmccall.com/2009/07/some-thoughts-on-unit-tests/#comment-12375021</link><description>&lt;p&gt;Some rules I apply when writing unit test -&lt;/p&gt;&lt;p&gt;1. Never write tests which rely on a resource outside of the code you're testing. i.e. Make mock objects for DAO's and stubs for external resources such as a web service end point.&lt;/p&gt;&lt;p&gt;2. Only test business logic. There's no point writing a test case which tests getters and setters, as you've said, and no point testing that framework you are using does the job it is supposed to do, that should be tested within that framework project itself. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John Hunsley</dc:creator><pubDate>Thu, 09 Jul 2009 08:57:31 -0000</pubDate></item></channel></rss>