<?xml version="1.0"?>
<rss version="2.0">
<channel>

  
<title>Kai`s Blog - mockito, spring & AbstractJUnit4SpringContextTests</title>
<link>http://www.kaigrabfelder.de/en/2011/04/02/mockito_spring_abstractjunit4springcontexttests.html</link>
<description>I know some people consider it bad practise. But nethertheless I still believe that there is sometimes no alternative to tests that include startup of spring application contexts and initialization of in memory database. Actually I quite like those tests ...</description>
<language>en</language>
<managingEditor>Kai Grabfelder</managingEditor>
<lastBuildDate>Sat, 02 Apr 2011 20:39:03 GMT</lastBuildDate>
  
  

  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Re: mockito, spring &amp; AbstractJUnit4SpringContextTests</title>
    <link>http://www.kaigrabfelder.de/en/2011/04/02/mockito_spring_abstractjunit4springcontexttests.html#comment1301776743978</link>
    <description>
      I don&#039;t think anyone considers it bad pratice to do tests involving databases or spring contexts. It&#039;s just a question of terminology. Such a Test can NEVER be a unit test (therefore your abstract class is badly named) as it is not testing a single unit of code. It is therefore always an integration test.
Nothing bad about doing integration tests using JUnit though.
    </description>
    <author>Frz</author>
    <comments>http://www.kaigrabfelder.de/en/2011/04/02/mockito_spring_abstractjunit4springcontexttests.html#comments</comments>
    <guid isPermaLink="true">http://www.kaigrabfelder.de/en/2011/04/02/mockito_spring_abstractjunit4springcontexttests.html#comment1301776743978</guid>
    <pubDate>Sat, 02 Apr 2011 20:39:03 GMT</pubDate>
  </item>
  
  </channel>
</rss>
