<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Programming for Scientists &#187; testing/debugging</title>
	<atom:link href="http://www.programming4scientists.com/category/testingdebugging/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.programming4scientists.com</link>
	<description>Software development wisdom and common-sense for the scientist-programmer</description>
	<lastBuildDate>Fri, 05 Feb 2010 15:27:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Testing and the scientist-programmer</title>
		<link>http://www.programming4scientists.com/2009/03/30/testing-and-the-scientist-programmer/</link>
		<comments>http://www.programming4scientists.com/2009/03/30/testing-and-the-scientist-programmer/#comments</comments>
		<pubDate>Mon, 30 Mar 2009 12:42:51 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[testing/debugging]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[science]]></category>
		<category><![CDATA[scientist-programmer]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.programming4scientists.com/?p=491</guid>
		<description><![CDATA[You do test your code, right?
Well?  We certainly hope so.
Testing can be a pain.  But it should also be a habit.  And we think it&#8217;s pretty uncontroversial to say that testing your code is a Good Thing.  The Scientist-Programmer often finds a tension between allocating effort to testing their code and effort to getting on [...]


Related posts:<ol><li><a href='http://www.programming4scientists.com/2009/12/17/scripting-for-science-papers/' rel='bookmark' title='Permanent Link: Scripting for science papers'>Scripting for science papers</a></li><li><a href='http://www.programming4scientists.com/2009/10/26/writing-code-for-a-big-scientific-collaboration/' rel='bookmark' title='Permanent Link: Writing code for a big scientific collaboration'>Writing code for a big scientific collaboration</a></li></ol>

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
		<wfw:commentRss>http://www.programming4scientists.com/2009/03/30/testing-and-the-scientist-programmer/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Seven ways to test your number-crunching code</title>
		<link>http://www.programming4scientists.com/2008/12/22/seven-ways-to-test-your-number-crunching-code/</link>
		<comments>http://www.programming4scientists.com/2008/12/22/seven-ways-to-test-your-number-crunching-code/#comments</comments>
		<pubDate>Mon, 22 Dec 2008 12:45:36 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[testing/debugging]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[science]]></category>

		<guid isPermaLink="false">http://www.programming4scientists.com/?p=376</guid>
		<description><![CDATA[Testing your code is important.  Pretty much vital, in fact.  This is because if you don&#8217;t test your code, you don&#8217;t know if it really works.  So an integral part of any software project is to come up with a good set of tests for your code.
Scientific code often involves numerical analysis of some kind.  [...]


Related posts:<ol><li><a href='http://www.programming4scientists.com/2009/10/26/writing-code-for-a-big-scientific-collaboration/' rel='bookmark' title='Permanent Link: Writing code for a big scientific collaboration'>Writing code for a big scientific collaboration</a></li><li><a href='http://www.programming4scientists.com/2009/12/17/scripting-for-science-papers/' rel='bookmark' title='Permanent Link: Scripting for science papers'>Scripting for science papers</a></li></ol>

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
		<wfw:commentRss>http://www.programming4scientists.com/2008/12/22/seven-ways-to-test-your-number-crunching-code/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Everyone wants to build, but no-one wants to do the maintenance&#8230;</title>
		<link>http://www.programming4scientists.com/2008/10/10/everyone-wants-to-build-but-no-one-wants-to-do-the-maintenance/</link>
		<comments>http://www.programming4scientists.com/2008/10/10/everyone-wants-to-build-but-no-one-wants-to-do-the-maintenance/#comments</comments>
		<pubDate>Fri, 10 Oct 2008 10:30:20 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[testing/debugging]]></category>
		<category><![CDATA[maintenance]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[sci]]></category>

		<guid isPermaLink="false">http://www.programming4scientists.com/?p=284</guid>
		<description><![CDATA[This is an article about maintaining your code once it&#8217;s written.  By this point, your project is useful.  People (possibly you) are using it to actually do some science.  However, there&#8217;s more still to be done and it would be a very bad plan to ignore this part. 
The need for maintenance
Fixing bugs never really [...]


Related posts:<ol><li><a href='http://www.programming4scientists.com/2009/09/29/the-programming-for-scientists-training-montage/' rel='bookmark' title='Permanent Link: The &#8216;Programming for Scientists&#8217; training montage'>The &#8216;Programming for Scientists&#8217; training montage</a></li><li><a href='http://www.programming4scientists.com/2009/10/26/writing-code-for-a-big-scientific-collaboration/' rel='bookmark' title='Permanent Link: Writing code for a big scientific collaboration'>Writing code for a big scientific collaboration</a></li></ol>

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
		<wfw:commentRss>http://www.programming4scientists.com/2008/10/10/everyone-wants-to-build-but-no-one-wants-to-do-the-maintenance/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The psychology of debugging</title>
		<link>http://www.programming4scientists.com/2008/10/06/the-psychology-of-debugging/</link>
		<comments>http://www.programming4scientists.com/2008/10/06/the-psychology-of-debugging/#comments</comments>
		<pubDate>Mon, 06 Oct 2008 13:57:53 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[testing/debugging]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[psychology]]></category>
		<category><![CDATA[science]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.programming4scientists.com/?p=268</guid>
		<description><![CDATA[Debugging is a very different task from coding and it benefits from a different mindset.  Finding bugs can take time and can involve a lot of trial, error and testing of different thoughts as to what might be going wrong, because there are lots of places in code where errors can hide.  This means you [...]


Related posts:<ol><li><a href='http://www.programming4scientists.com/2009/09/29/the-programming-for-scientists-training-montage/' rel='bookmark' title='Permanent Link: The &#8216;Programming for Scientists&#8217; training montage'>The &#8216;Programming for Scientists&#8217; training montage</a></li><li><a href='http://www.programming4scientists.com/2009/12/17/scripting-for-science-papers/' rel='bookmark' title='Permanent Link: Scripting for science papers'>Scripting for science papers</a></li></ol>

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
		<wfw:commentRss>http://www.programming4scientists.com/2008/10/06/the-psychology-of-debugging/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Four ways to find invisible bugs</title>
		<link>http://www.programming4scientists.com/2008/09/29/4-ways-to-find-invisible-bugs/</link>
		<comments>http://www.programming4scientists.com/2008/09/29/4-ways-to-find-invisible-bugs/#comments</comments>
		<pubDate>Mon, 29 Sep 2008 11:07:00 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[testing/debugging]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[science]]></category>

		<guid isPermaLink="false">http://www.programming4scientists.com/?p=262</guid>
		<description><![CDATA[&#8220;I just can&#8217;t find what&#8217;s wrong with my code&#8230;&#8221;

Sometimes you just can&#8217;t see why your code isn&#8217;t working.  It&#8217;s clearly broken , but you have no idea why.  Frustrating, isn&#8217;t it? Happily, there are good tactics you can employ when this happens to find the problem and fix it.
Get a second pair of eyes
Sometimes having [...]


Related posts:<ol><li><a href='http://www.programming4scientists.com/2009/09/29/the-programming-for-scientists-training-montage/' rel='bookmark' title='Permanent Link: The &#8216;Programming for Scientists&#8217; training montage'>The &#8216;Programming for Scientists&#8217; training montage</a></li><li><a href='http://www.programming4scientists.com/2009/10/26/writing-code-for-a-big-scientific-collaboration/' rel='bookmark' title='Permanent Link: Writing code for a big scientific collaboration'>Writing code for a big scientific collaboration</a></li><li><a href='http://www.programming4scientists.com/2009/12/17/scripting-for-science-papers/' rel='bookmark' title='Permanent Link: Scripting for science papers'>Scripting for science papers</a></li></ol>

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
		<wfw:commentRss>http://www.programming4scientists.com/2008/09/29/4-ways-to-find-invisible-bugs/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Testing and debugging computer code &#8211; three key questions to ask</title>
		<link>http://www.programming4scientists.com/2008/08/29/testing-and-debugging-computer-code-three-key-questions-to-ask/</link>
		<comments>http://www.programming4scientists.com/2008/08/29/testing-and-debugging-computer-code-three-key-questions-to-ask/#comments</comments>
		<pubDate>Fri, 29 Aug 2008 14:11:37 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[testing/debugging]]></category>
		<category><![CDATA[debugging]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.programming4scientists.com/?p=109</guid>
		<description><![CDATA[This is the first in a series of articles on how to test and debug your code.  We start by with three key questions that you can ask about your code, that will guide you as to whether your code has been tested and debugged enough for it to be worth using.
At this point in [...]


Related posts:<ol><li><a href='http://www.programming4scientists.com/2009/10/26/writing-code-for-a-big-scientific-collaboration/' rel='bookmark' title='Permanent Link: Writing code for a big scientific collaboration'>Writing code for a big scientific collaboration</a></li><li><a href='http://www.programming4scientists.com/2009/12/17/scripting-for-science-papers/' rel='bookmark' title='Permanent Link: Scripting for science papers'>Scripting for science papers</a></li></ol>

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
		<wfw:commentRss>http://www.programming4scientists.com/2008/08/29/testing-and-debugging-computer-code-three-key-questions-to-ask/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
