<?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 for Paul Moser</title>
	<atom:link href="http://blog.paulmoser.co.uk/index.php/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.paulmoser.co.uk</link>
	<description>So much to learn but so little time</description>
	<lastBuildDate>Fri, 26 Dec 2008 01:15:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Ruby-on-Rails on Ubuntu 8.04 by Diego Alban</title>
		<link>http://blog.paulmoser.co.uk/index.php/2008/10/31/ruby-on-rails-on-ubuntu-804/comment-page-1/#comment-16560</link>
		<dc:creator>Diego Alban</dc:creator>
		<pubDate>Fri, 26 Dec 2008 01:15:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2008/10/31/ruby-on-rails-on-ubuntu-804/#comment-16560</guid>
		<description>Thanks! It worked perfectly for Ubuntu 8.10 (Ibex). (I&#039;m also using Sequel instead of ActiveRecord.)</description>
		<content:encoded><![CDATA[<p>Thanks! It worked perfectly for Ubuntu 8.10 (Ibex). (I&#8217;m also using Sequel instead of ActiveRecord.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on White screen after login to X on Linux (Ubuntu) by jobo</title>
		<link>http://blog.paulmoser.co.uk/index.php/2008/10/31/white-screen-after-login-to-x-on-linux-ubuntu/comment-page-1/#comment-16176</link>
		<dc:creator>jobo</dc:creator>
		<pubDate>Tue, 16 Dec 2008 09:08:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2008/10/31/white-screen-after-login-to-x-on-linux-ubuntu/#comment-16176</guid>
		<description>for me the problem appears while upgrade my distribution. i had thinking change the driver to &quot;vesa&quot; for do installation but i m not sure if it ll work!!</description>
		<content:encoded><![CDATA[<p>for me the problem appears while upgrade my distribution. i had thinking change the driver to &#8220;vesa&#8221; for do installation but i m not sure if it ll work!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t write tests to test your code by Kekoa</title>
		<link>http://blog.paulmoser.co.uk/index.php/2008/04/22/dont-write-tests-to-test-your-code/comment-page-1/#comment-15883</link>
		<dc:creator>Kekoa</dc:creator>
		<pubDate>Tue, 09 Dec 2008 21:21:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2008/04/22/dont-write-tests-to-test-your-code/#comment-15883</guid>
		<description>Although I think your point is very valid, I think some testing is better than no testing.  I have seen it be very difficult to change the mindset of seasoned programmers.  They just don&#039;t get TDD, and hate testing in general.

Even if testing is done out of order I feel like there is some benefit, mainly that you step through your own logic twice, and have an opportunity to catch errors in your reasoning.  

In my experience TDD is much easier in the earlier stages, later on, you end up having to still change both your tests and code when things change.</description>
		<content:encoded><![CDATA[<p>Although I think your point is very valid, I think some testing is better than no testing.  I have seen it be very difficult to change the mindset of seasoned programmers.  They just don&#8217;t get TDD, and hate testing in general.</p>
<p>Even if testing is done out of order I feel like there is some benefit, mainly that you step through your own logic twice, and have an opportunity to catch errors in your reasoning.  </p>
<p>In my experience TDD is much easier in the earlier stages, later on, you end up having to still change both your tests and code when things change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on White screen after login to X on Linux (Ubuntu) by duongchi</title>
		<link>http://blog.paulmoser.co.uk/index.php/2008/10/31/white-screen-after-login-to-x-on-linux-ubuntu/comment-page-1/#comment-14983</link>
		<dc:creator>duongchi</dc:creator>
		<pubDate>Sat, 15 Nov 2008 02:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2008/10/31/white-screen-after-login-to-x-on-linux-ubuntu/#comment-14983</guid>
		<description>Thank you very much! I have had the same problem after I ran &quot;sudo gem update â€“system&quot;. I was so sorrow with it but I can fix thanks to your instruction, many thanks :)</description>
		<content:encoded><![CDATA[<p>Thank you very much! I have had the same problem after I ran &#8220;sudo gem update â€“system&#8221;. I was so sorrow with it but I can fix thanks to your instruction, many thanks <img src='http://blog.paulmoser.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruby-on-Rails on Ubuntu 8.04 by Dario</title>
		<link>http://blog.paulmoser.co.uk/index.php/2008/10/31/ruby-on-rails-on-ubuntu-804/comment-page-1/#comment-14621</link>
		<dc:creator>Dario</dc:creator>
		<pubDate>Sun, 02 Nov 2008 18:20:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2008/10/31/ruby-on-rails-on-ubuntu-804/#comment-14621</guid>
		<description>Thank you very much for this post! I have the exact same problem since friday, I found your post and fix it :)

Regards.</description>
		<content:encoded><![CDATA[<p>Thank you very much for this post! I have the exact same problem since friday, I found your post and fix it <img src='http://blog.paulmoser.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit testing interface implementations by Contract Tests with TestNG: update</title>
		<link>http://blog.paulmoser.co.uk/index.php/2007/02/25/unit-testing-interface-implementations/comment-page-1/#comment-12740</link>
		<dc:creator>Contract Tests with TestNG: update</dc:creator>
		<pubDate>Fri, 22 Aug 2008 23:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2007/02/25/unit-testing-interface-implementations/#comment-12740</guid>
		<description>[...] functionality of abstract classes works properly in all concrete subclasses. Certainly this has been mentioned before, generally under the name Abstract Tests or Contract Tests. Also, the idea seems [...]</description>
		<content:encoded><![CDATA[<p>[...] functionality of abstract classes works properly in all concrete subclasses. Certainly this has been mentioned before, generally under the name Abstract Tests or Contract Tests. Also, the idea seems [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How does your team sit? by Milan Magudia</title>
		<link>http://blog.paulmoser.co.uk/index.php/2007/12/11/how-does-your-team-sit/comment-page-1/#comment-10455</link>
		<dc:creator>Milan Magudia</dc:creator>
		<pubDate>Fri, 23 May 2008 14:26:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2007/12/11/how-does-your-team-sit/#comment-10455</guid>
		<description>Like cars everyone knows the worst place to sit is the middle</description>
		<content:encoded><![CDATA[<p>Like cars everyone knows the worst place to sit is the middle</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit testing interface implementations by Ilya Bobir</title>
		<link>http://blog.paulmoser.co.uk/index.php/2007/02/25/unit-testing-interface-implementations/comment-page-1/#comment-6608</link>
		<dc:creator>Ilya Bobir</dc:creator>
		<pubDate>Sat, 15 Dec 2007 07:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2007/02/25/unit-testing-interface-implementations/#comment-6608</guid>
		<description>It constantly gives me an error.  Please check the server logs. =)</description>
		<content:encoded><![CDATA[<p>It constantly gives me an error.  Please check the server logs. =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit testing interface implementations by Ilya Bobir</title>
		<link>http://blog.paulmoser.co.uk/index.php/2007/02/25/unit-testing-interface-implementations/comment-page-1/#comment-6607</link>
		<dc:creator>Ilya Bobir</dc:creator>
		<pubDate>Sat, 15 Dec 2007 07:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2007/02/25/unit-testing-interface-implementations/#comment-6607</guid>
		<description>For some reason I can not submit the rest of my post :(</description>
		<content:encoded><![CDATA[<p>For some reason I can not submit the rest of my post <img src='http://blog.paulmoser.co.uk/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit testing interface implementations by Ilya Bobir</title>
		<link>http://blog.paulmoser.co.uk/index.php/2007/02/25/unit-testing-interface-implementations/comment-page-1/#comment-6606</link>
		<dc:creator>Ilya Bobir</dc:creator>
		<pubDate>Sat, 15 Dec 2007 07:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2007/02/25/unit-testing-interface-implementations/#comment-6606</guid>
		<description>Suites can be connected to form a tree.  A suite for the interface contract can be added as a child to the suite that tests the class.

About telling which implementation of the interface to test, it is quite easy with JUint 3 where you are creating suites yourself.  You can just add a method to the suite that will take an implementation factory and will propagate it into all contained tests.  Then you need to do a call to supply the factory in addition to attaching the interface test suite as a child to your class test suite.</description>
		<content:encoded><![CDATA[<p>Suites can be connected to form a tree.  A suite for the interface contract can be added as a child to the suite that tests the class.</p>
<p>About telling which implementation of the interface to test, it is quite easy with JUint 3 where you are creating suites yourself.  You can just add a method to the suite that will take an implementation factory and will propagate it into all contained tests.  Then you need to do a call to supply the factory in addition to attaching the interface test suite as a child to your class test suite.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
