<?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: Using the OSX Console.app to aid Grails Test Driven Development</title>
	<atom:link href="http://naleid.com/blog/2008/03/13/using-the-osx-consoleapp-to-aid-grails-test-driven-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://naleid.com/blog/2008/03/13/using-the-osx-consoleapp-to-aid-grails-test-driven-development/</link>
	<description>Groovy, Grails and OS X tips and tricks</description>
	<lastBuildDate>Sat, 31 Jul 2010 11:43:17 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ted Naleid &#187; Grails Testing Command Line Aliases</title>
		<link>http://naleid.com/blog/2008/03/13/using-the-osx-consoleapp-to-aid-grails-test-driven-development/comment-page-1/#comment-1442</link>
		<dc:creator>Ted Naleid &#187; Grails Testing Command Line Aliases</dc:creator>
		<pubDate>Sun, 14 Jun 2009 05:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://tednaleid.wordpress.com/?p=3#comment-1442</guid>
		<description>[...] These aliases are all set up to run the &#8220;testlog&#8221; alias if a failing exit code is returned from the test run. This searched through all of the testlog results for any failures and automatically opens up each failing testlog in the OSX Console.app (if you&#8217;re on another platform, just substitute a different editor). I wrote a more detailed post a while ago about how nice Console.app is for looking at grails test logs. [...]</description>
		<content:encoded><![CDATA[<p>[...] These aliases are all set up to run the &#8220;testlog&#8221; alias if a failing exit code is returned from the test run. This searched through all of the testlog results for any failures and automatically opens up each failing testlog in the OSX Console.app (if you&#8217;re on another platform, just substitute a different editor). I wrote a more detailed post a while ago about how nice Console.app is for looking at grails test logs. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Taylor</title>
		<link>http://naleid.com/blog/2008/03/13/using-the-osx-consoleapp-to-aid-grails-test-driven-development/comment-page-1/#comment-27</link>
		<dc:creator>Matthew Taylor</dc:creator>
		<pubDate>Tue, 22 Apr 2008 11:12:16 +0000</pubDate>
		<guid isPermaLink="false">http://tednaleid.wordpress.com/?p=3#comment-27</guid>
		<description>Great tip!  I started using this immediately.</description>
		<content:encoded><![CDATA[<p>Great tip!  I started using this immediately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Deville</title>
		<link>http://naleid.com/blog/2008/03/13/using-the-osx-consoleapp-to-aid-grails-test-driven-development/comment-page-1/#comment-4</link>
		<dc:creator>James Deville</dc:creator>
		<pubDate>Sat, 15 Mar 2008 07:20:22 +0000</pubDate>
		<guid isPermaLink="false">http://tednaleid.wordpress.com/?p=3#comment-4</guid>
		<description>This is an awesome tip for general logs. I&#039;ll have to checkout console more!</description>
		<content:encoded><![CDATA[<p>This is an awesome tip for general logs. I&#8217;ll have to checkout console more!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://naleid.com/blog/2008/03/13/using-the-osx-consoleapp-to-aid-grails-test-driven-development/comment-page-1/#comment-3</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 13 Mar 2008 11:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://tednaleid.wordpress.com/?p=3#comment-3</guid>
		<description>Nice trick, Ted!  I currently use an alias to open the reports directory using TextMate and then do a &quot;Find&quot; to track down the failed test(s).  This will make it much easier for me to get to the information I need when a test fails!</description>
		<content:encoded><![CDATA[<p>Nice trick, Ted!  I currently use an alias to open the reports directory using TextMate and then do a &#8220;Find&#8221; to track down the failed test(s).  This will make it much easier for me to get to the information I need when a test fails!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Indy Nagpal</title>
		<link>http://naleid.com/blog/2008/03/13/using-the-osx-consoleapp-to-aid-grails-test-driven-development/comment-page-1/#comment-2</link>
		<dc:creator>Indy Nagpal</dc:creator>
		<pubDate>Thu, 13 Mar 2008 08:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://tednaleid.wordpress.com/?p=3#comment-2</guid>
		<description>Ah. A very useful blog post. Thanks!

I love Console! I use it all the time to trace Flash log as well as ColdFusion log files. I use it for custom log files. But didn&#039;t know one could setup alias like this.

Will try it out soon.</description>
		<content:encoded><![CDATA[<p>Ah. A very useful blog post. Thanks!</p>
<p>I love Console! I use it all the time to trace Flash log as well as ColdFusion log files. I use it for custom log files. But didn&#8217;t know one could setup alias like this.</p>
<p>Will try it out soon.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
