<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>CodingClues - Latest Comments in Problems with Assertions in JUnit tests using Eclipse</title><link>http://codingclues.disqus.com/</link><description></description><atom:link href="http://codingclues.disqus.com/problems_with_assertions_in_junit_tests_using_eclipse/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 20 Jan 2009 09:35:42 -0000</lastBuildDate><item><title>Re: Problems with Assertions in JUnit tests using Eclipse</title><link>http://codingclues.eu/2008/assertions-in-eclipse/#comment-5392456</link><description>&lt;p&gt;Eclipse v. 3.1comes with JUnit built into the Workbench. Eclipse allows you to quickly create test case classes and test suite classes to write your test code in. With Eclipse, Test Driven Development (TDD), becomes very easy to organize and implement.&lt;/p&gt;

&lt;p&gt; &lt;b&gt;&lt;a href="http://add-blogbanner.blogspot.com" rel="nofollow"&gt;http://add-blogbanner.blogspot...&lt;/a&gt;&lt;/b&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">deepakp9</dc:creator><pubDate>Tue, 20 Jan 2009 09:35:42 -0000</pubDate></item><item><title>Re: Problems with Assertions in JUnit tests using Eclipse</title><link>http://codingclues.eu/2008/assertions-in-eclipse/#comment-3855781</link><description>&lt;p&gt;Another thing to keep in mind: maven will run each test in its own JVM, eclipse will run them in the same JVM. So do your cleanup work in the unit tests so you leave no static data somewhere that influences your tests.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">guruz</dc:creator><pubDate>Mon, 30 Jun 2008 11:04:02 -0000</pubDate></item></channel></rss>
