<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Kai`s Blog - mockito tag</title>
  <link>http://www.kaigrabfelder.de/en/tags/mockito/</link>
  <description>yet another blog about java, software, movies and more...</description>
  <language>en</language>
  <copyright>Kai Grabfelder</copyright>
  <lastBuildDate>Sat, 29 Oct 2011 12:44:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>mockito, spring &amp; 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 because if I don&#039;t include my database layer and my spring application contexts in my test I always have a bad felling about the quality of my software....&lt;p&gt;&lt;a href=&#034;http://www.kaigrabfelder.de/en/2011/04/02/mockito_spring_abstractjunit4springcontexttests.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <category>java</category>
    
    <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</guid>
    <pubDate>Sat, 02 Apr 2011 16:02:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>

