<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Python Testing</title>
	
	<link>http://pythontesting.net</link>
	<description>Python Test Frameworks and Strategies</description>
	<lastBuildDate>Wed, 22 May 2013 14:23:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/PythonTesting" /><feedburner:info uri="pythontesting" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>PythonTesting</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>How not to test, part 1</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/nYDBUxFjkG4/</link>
		<comments>http://pythontesting.net/strategy/complete-coverage-testing/#comments</comments>
		<pubDate>Tue, 21 May 2013 14:14:49 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Strategy]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=552</guid>
		<description>&lt;p&gt;or Complete coverage testing or More is Better testing Update 5/22/13: I&amp;#8217;ve received several criticisms of this post. Most of them constructive. :) I&amp;#8217;d like to take some time to re-read the post, re-read the feedback, and compose a more coherent statement about my thoughts on the matter. I agree with some points of my [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/strategy/complete-coverage-testing/"&gt;How not to test, part 1&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/nYDBUxFjkG4" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/strategy/complete-coverage-testing/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://pythontesting.net/strategy/complete-coverage-testing/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=complete-coverage-testing</feedburner:origLink></item>
		<item>
		<title>pytest debug print logging in real time</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/UMYQ--WmUH8/</link>
		<comments>http://pythontesting.net/framework/pytest/pytest-logging-real-time/#comments</comments>
		<pubDate>Thu, 04 Apr 2013 02:23:18 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[pytest]]></category>
		<category><![CDATA[debug]]></category>
		<category><![CDATA[logging]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=524</guid>
		<description>&lt;p&gt;There are many circumstances where it&amp;#8217;s really great to display the output of a test while a test is running, and not wait until the end. In this post, I&amp;#8217;m going to describe my method for getting around pytest&amp;#8217;s output capture mechanism, so that I can see my debug print/logging statements in real time. Fast [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/framework/pytest/pytest-logging-real-time/"&gt;pytest debug print logging in real time&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/UMYQ--WmUH8" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/framework/pytest/pytest-logging-real-time/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		<feedburner:origLink>http://pythontesting.net/framework/pytest/pytest-logging-real-time/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=pytest-logging-real-time</feedburner:origLink></item>
		<item>
		<title>regex search and replace example scripts</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/fYjK6gGLOyI/</link>
		<comments>http://pythontesting.net/python/regex-search-replace-examples/#comments</comments>
		<pubDate>Fri, 08 Feb 2013 03:55:43 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Python]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[regex]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=438</guid>
		<description>&lt;p&gt;Search and replace is such a common task that it should be a tool that&amp;#8217;s in every command line script author&amp;#8217;s toolbox. There are probably endless solutions to the problem. I&amp;#8217;ve put together my standard methods for tackling the problem. I&amp;#8217;ll also show similar Perl versions, mainly for comparisons. use models using Python with a [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/python/regex-search-replace-examples/"&gt;regex search and replace example scripts&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/fYjK6gGLOyI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/python/regex-search-replace-examples/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://pythontesting.net/python/regex-search-replace-examples/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=regex-search-replace-examples</feedburner:origLink></item>
		<item>
		<title>Markdown.py passes first 3 tests</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/vSxWSDij5-w/</link>
		<comments>http://pythontesting.net/markdown/markdown-py-passes-first-3-tests/#comments</comments>
		<pubDate>Sun, 03 Feb 2013 05:56:25 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Markdown]]></category>
		<category><![CDATA[markdown]]></category>
		<category><![CDATA[pytest]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=428</guid>
		<description>&lt;p&gt;Just pushed up an update to markdown.py and test_markdown_pytest.py to github Passing first 3 tests now. Non-marked lines em tags strong tags Update: I posted this, then felt bad that it was so short, so removed it. However, a notification already had gone out on twitter and the rss feed. So I moved it back [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/markdown/markdown-py-passes-first-3-tests/"&gt;Markdown.py passes first 3 tests&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/vSxWSDij5-w" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/markdown/markdown-py-passes-first-3-tests/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		<feedburner:origLink>http://pythontesting.net/markdown/markdown-py-passes-first-3-tests/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=markdown-py-passes-first-3-tests</feedburner:origLink></item>
		<item>
		<title>nose introduction</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/m2pbXMP1l5c/</link>
		<comments>http://pythontesting.net/framework/nose-introduction/#comments</comments>
		<pubDate>Tue, 29 Jan 2013 15:51:12 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[nose]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=414</guid>
		<description>&lt;p&gt;This post has several examples, and covers fixtures, test discovery, asserts, running options, and running unittests and doctests. Nose&amp;#8217;s tagline is &amp;#8220;nose extends unittest to make testing easier&amp;#8221;. It&amp;#8217;s is a fairly well known python unit test framework, and can run doctests, unittests, and &amp;#8220;no boilerplate&amp;#8221; tests. It is a good candidate for a go-to [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/framework/nose-introduction/"&gt;nose introduction&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/m2pbXMP1l5c" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/framework/nose-introduction/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://pythontesting.net/framework/nose-introduction/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=nose-introduction</feedburner:origLink></item>
		<item>
		<title>pytest introduction</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/_f0FYGMcYQQ/</link>
		<comments>http://pythontesting.net/framework/pytest-introduction/#comments</comments>
		<pubDate>Tue, 15 Jan 2013 13:36:34 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[pytest]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=403</guid>
		<description>&lt;p&gt;I think of pytest as the run-anything, no boilerplate, no required api, use-this-unless-you-have-a-reason-not-to test framework. This is really where testing gets fun. As with previous intro&amp;#8217;s on this site, I&amp;#8217;ll run through an overview, then a simple example, then throw pytest at my markdown.py project. I&amp;#8217;ll also cover fixtures, test discovery, and running unittests with [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/framework/pytest-introduction/"&gt;pytest introduction&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/_f0FYGMcYQQ" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/framework/pytest-introduction/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		<feedburner:origLink>http://pythontesting.net/framework/pytest-introduction/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=pytest-introduction</feedburner:origLink></item>
		<item>
		<title>Confession … I still use perl on the command line</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/edg9IH06BkI/</link>
		<comments>http://pythontesting.net/python/command-line-perl/#comments</comments>
		<pubDate>Wed, 09 Jan 2013 00:00:04 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Python]]></category>
		<category><![CDATA[command line]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=389</guid>
		<description>&lt;p&gt;I have a confession to make. I still use Perl. Regularly. But mostly as a command line tool. Is that a reason? or an excuse? When I started using Python regularly, I tried to replace my Perl usage. Nothing against Perl, I just wanted to force myself to use Python to aid in my learning [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/python/command-line-perl/"&gt;Confession &amp;#8230; I still use perl on the command line&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/edg9IH06BkI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/python/command-line-perl/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		<feedburner:origLink>http://pythontesting.net/python/command-line-perl/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=command-line-perl</feedburner:origLink></item>
		<item>
		<title>unittest introduction</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/NiyPHJy8ZIE/</link>
		<comments>http://pythontesting.net/framework/unittest-introduction/#comments</comments>
		<pubDate>Fri, 04 Jan 2013 05:22:18 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[pyUnit]]></category>
		<category><![CDATA[unittest]]></category>
		<category><![CDATA[xUnit]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=334</guid>
		<description>&lt;p&gt;The unittest test framework is python&amp;#8217;s xUnit style framework. It is a standard module that you already have if you&amp;#8217;ve got python version 2.1 or greater. In this post, I&amp;#8217;ll cover the basics of how to create and run a simple test using unittest. Then I&amp;#8217;ll show how I&amp;#8217;m using it to test markdown.py. Overview [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/framework/unittest-introduction/"&gt;unittest introduction&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/NiyPHJy8ZIE" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/framework/unittest-introduction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://pythontesting.net/framework/unittest-introduction/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=unittest-introduction</feedburner:origLink></item>
		<item>
		<title>tip: interactive python from cygwin when using windows python install</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/GnwrB2Vl8bA/</link>
		<comments>http://pythontesting.net/python/interactive-python-cygwin-bas/#comments</comments>
		<pubDate>Mon, 17 Dec 2012 16:00:12 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Python]]></category>
		<category><![CDATA[cygwin]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=339</guid>
		<description>&lt;p&gt;Remember to use the &amp;#8216;-i&amp;#8217; flag when starting an interactive python session from cygwin if you&amp;#8217;ve installed python with a windows installer. cygwin session (bad): &gt; python &amp;#124; (... nothing ... perpetual annoying blinking cursor ... grrr) cygwin session (good): &gt; python -i &lt; -- version info deleted -- &gt; &gt;&gt;&gt; print 'ABJPGRSJWRPF' ABJPGRSJWRPF &gt;&gt;&gt; [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/python/interactive-python-cygwin-bas/"&gt;tip: interactive python from cygwin when using windows python install&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/GnwrB2Vl8bA" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/python/interactive-python-cygwin-bas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://pythontesting.net/python/interactive-python-cygwin-bas/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=interactive-python-cygwin-bas</feedburner:origLink></item>
		<item>
		<title>Poll Results: test frameworks</title>
		<link>http://feedproxy.google.com/~r/PythonTesting/~3/tJpLinspt10/</link>
		<comments>http://pythontesting.net/meta/poll-results-test-frameworks/#comments</comments>
		<pubDate>Fri, 14 Dec 2012 06:10:42 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Meta]]></category>
		<category><![CDATA[doctest]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[nose]]></category>
		<category><![CDATA[pytest]]></category>
		<category><![CDATA[unittest]]></category>

		<guid isPermaLink="false">http://pythontesting.net/?p=327</guid>
		<description>&lt;p&gt;Well, the poll I put up a couple weeks ago has 125 votes last I checked. Results nose, 42 votes pytest, 32 votes unittest, 29 votes doctest, 18 votes other, 4 votes The other votes were: twisted trial (also mentioned in a comment) pyVows attest zope.testing Commentary This is mostly what I expected. So I [...]&lt;/p&gt;&lt;p&gt;The post &lt;a href="http://pythontesting.net/meta/poll-results-test-frameworks/"&gt;Poll Results: test frameworks&lt;/a&gt; appeared first on &lt;a href="http://pythontesting.net"&gt;Python Testing&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PythonTesting/~4/tJpLinspt10" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://pythontesting.net/meta/poll-results-test-frameworks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://pythontesting.net/meta/poll-results-test-frameworks/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=poll-results-test-frameworks</feedburner:origLink></item>
	</channel>
</rss><!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced

 Served from: pythontesting.net @ 2013-05-22 06:33:20 by W3 Total Cache -->
