<?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: Python Regression tests</title>
	<atom:link href="http://www.j5live.com/2005/08/24/python-regression-tests/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.j5live.com/2005/08/24/python-regression-tests/</link>
	<description>Where the urethane hits the pavement</description>
	<lastBuildDate>Fri, 27 Aug 2010 16:17:13 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James</title>
		<link>http://www.j5live.com/2005/08/24/python-regression-tests/comment-page-1/#comment-1664</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 25 Aug 2005 05:43:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.martianrock.com/?p=126#comment-1664</guid>
		<description>Currently in test-client.py, you have a number of tests:

 * connecting to the session bus

 * resolving an object on the session bus

 * narrowing to a particular interface

 * introspecting the object

 * testing various ways of invoking methods on the object

 * testing various inputs/outputs of methods on the object

With a test suite, you usually want to run all the tests, and see which ones fail.  If you stop running tests after the first error, then you won&#039;t know if the later tests pass.

The docs on the Python unit test framework are here:
  http://www.python.org/doc/current/lib/module-unittest.html

The &quot;basic example&quot; page shows the common way to structure the tests.</description>
		<content:encoded><![CDATA[<p>Currently in test-client.py, you have a number of tests:</p>
<p> * connecting to the session bus</p>
<p> * resolving an object on the session bus</p>
<p> * narrowing to a particular interface</p>
<p> * introspecting the object</p>
<p> * testing various ways of invoking methods on the object</p>
<p> * testing various inputs/outputs of methods on the object</p>
<p>With a test suite, you usually want to run all the tests, and see which ones fail.  If you stop running tests after the first error, then you won&#8217;t know if the later tests pass.</p>
<p>The docs on the Python unit test framework are here:<br />
  <a href="http://www.python.org/doc/current/lib/module-unittest.html" rel="nofollow">http://www.python.org/doc/current/lib/module-unittest.html</a></p>
<p>The &#8220;basic example&#8221; page shows the common way to structure the tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J5</title>
		<link>http://www.j5live.com/2005/08/24/python-regression-tests/comment-page-1/#comment-1663</link>
		<dc:creator>J5</dc:creator>
		<pubDate>Thu, 25 Aug 2005 01:20:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.martianrock.com/?p=126#comment-1663</guid>
		<description>With make check you sort of want to stop when one test fails, fix it up and then go on.   I wouldn&#039;t object however is someone sent me a patch as long as it doesn&#039;t make it any harder for people to implement tests.</description>
		<content:encoded><![CDATA[<p>With make check you sort of want to stop when one test fails, fix it up and then go on.   I wouldn&#8217;t object however is someone sent me a patch as long as it doesn&#8217;t make it any harder for people to implement tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.j5live.com/2005/08/24/python-regression-tests/comment-page-1/#comment-1662</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 25 Aug 2005 01:13:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.martianrock.com/?p=126#comment-1662</guid>
		<description>Have you considered using the Python unit testing framework for the test-client.py implementation?  It seems like it would be well suited for this kind of thing, and would continue to run tests after the first failure (i.e. it&#039;d still fail, but you&#039;d know if one test failed as opposed to all the tests after the failing one).</description>
		<content:encoded><![CDATA[<p>Have you considered using the Python unit testing framework for the test-client.py implementation?  It seems like it would be well suited for this kind of thing, and would continue to run tests after the first failure (i.e. it&#8217;d still fail, but you&#8217;d know if one test failed as opposed to all the tests after the failing one).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
