<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Maybe Tests Don&#8217;t Belong in Your Project</title>
	<atom:link href="http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/feed/" rel="self" type="application/rss+xml" />
	<link>http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/</link>
	<description>Technology and Geek Stuff by Eric Burke</description>
	<lastBuildDate>Thu, 04 Nov 2010 22:37:00 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: lumpynose</title>
		<link>http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/comment-page-1/#comment-57</link>
		<dc:creator>lumpynose</dc:creator>
		<pubDate>Fri, 21 Sep 2007 20:47:57 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/#comment-57</guid>
		<description>I actually use this method in my latest self-designated project, a web based photo album (original idea, eh?).  In some ways it seems a lot better for deployment; for example, all of your jars needed for testing are in the test project (jmock, junit, spring-mock, etc.) so there&#039;s less crud to filter out when making the war file; similar to the problem of filtering out the test classes as you pointed out.  And I have a separate log4j.xml set up for my test project.  But the downside is if you&#039;re working in Eclipse, it&#039;s not too savvy about this.  It does have this thing where one project can depend on the other, so my test project depends on the main project, but the Spring xml config files aren&#039;t found correctly.  I forget the details but I have my applicationContext.xml and the two xml files it imports in my WEB-INF directory in the test project.  Other than that I think it&#039;s really great having them entirely separated.</description>
		<content:encoded><![CDATA[<p>I actually use this method in my latest self-designated project, a web based photo album (original idea, eh?).  In some ways it seems a lot better for deployment; for example, all of your jars needed for testing are in the test project (jmock, junit, spring-mock, etc.) so there&#8217;s less crud to filter out when making the war file; similar to the problem of filtering out the test classes as you pointed out.  And I have a separate log4j.xml set up for my test project.  But the downside is if you&#8217;re working in Eclipse, it&#8217;s not too savvy about this.  It does have this thing where one project can depend on the other, so my test project depends on the main project, but the Spring xml config files aren&#8217;t found correctly.  I forget the details but I have my applicationContext.xml and the two xml files it imports in my WEB-INF directory in the test project.  Other than that I think it&#8217;s really great having them entirely separated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Burke</title>
		<link>http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/comment-page-1/#comment-47</link>
		<dc:creator>Eric Burke</dc:creator>
		<pubDate>Wed, 19 Sep 2007 14:24:49 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/#comment-47</guid>
		<description>JR, yes, that&#039;s how I envisioned it. Each version of the app would have a corresponding test release. Although I suppose if you release a &quot;bug fix only&quot; release of your app, I wonder if you really need a whole new version of the tests? Maybe you only need new test versions when you break APIs in the core app.</description>
		<content:encoded><![CDATA[<p>JR, yes, that&#8217;s how I envisioned it. Each version of the app would have a corresponding test release. Although I suppose if you release a &#8220;bug fix only&#8221; release of your app, I wonder if you really need a whole new version of the tests? Maybe you only need new test versions when you break APIs in the core app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JR</title>
		<link>http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/comment-page-1/#comment-46</link>
		<dc:creator>JR</dc:creator>
		<pubDate>Wed, 19 Sep 2007 13:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/#comment-46</guid>
		<description>I see the benefits to the approach, but what was your take on how tests get versioned?  I assume that you&#039;d still version your tests as you version your source base, but have the ability to run the source for 2.2 against the test sources of 2.2, 2.1, 2.0, etc to see if compatibility still exists.</description>
		<content:encoded><![CDATA[<p>I see the benefits to the approach, but what was your take on how tests get versioned?  I assume that you&#8217;d still version your tests as you version your source base, but have the ability to run the source for 2.2 against the test sources of 2.2, 2.1, 2.0, etc to see if compatibility still exists.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Böckling</title>
		<link>http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/comment-page-1/#comment-41</link>
		<dc:creator>Michael Böckling</dc:creator>
		<pubDate>Mon, 17 Sep 2007 06:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/#comment-41</guid>
		<description>You can do that easily with Maven 2. It uses different directory trees for app and test code, and it supports the automatic creation of a appname-tests.jar artifact that can be stored in the repository. I&#039;m not sure if it would be all that easy to really perform the unit-tests automatically with earlier versions, though.</description>
		<content:encoded><![CDATA[<p>You can do that easily with Maven 2. It uses different directory trees for app and test code, and it supports the automatic creation of a appname-tests.jar artifact that can be stored in the repository. I&#8217;m not sure if it would be all that easy to really perform the unit-tests automatically with earlier versions, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/comment-page-1/#comment-39</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Mon, 17 Sep 2007 05:42:03 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/16/maybe-tests-dont-belong-in-your-project/#comment-39</guid>
		<description>I like it!</description>
		<content:encoded><![CDATA[<p>I like it!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.236 seconds -->

