<?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>Test Me &#187; Software</title>
	<atom:link href="http://elblinkin.info/category/software/feed/" rel="self" type="application/rss+xml" />
	<link>http://elblinkin.info</link>
	<description>Rantings on Quality</description>
	<lastBuildDate>Tue, 21 Feb 2012 17:47:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>New Addition to CSRunner: php -l</title>
		<link>http://elblinkin.info/2012/02/new-addition-to-csrunner-php-l/</link>
		<comments>http://elblinkin.info/2012/02/new-addition-to-csrunner-php-l/#comments</comments>
		<pubDate>Tue, 21 Feb 2012 17:47:49 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[clean code]]></category>
		<category><![CDATA[Continuous Integration]]></category>
		<category><![CDATA[developer testing]]></category>
		<category><![CDATA[Jenkins]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[phpcs]]></category>
		<category><![CDATA[PHPUnit]]></category>
		<category><![CDATA[PHP_CodeSniffer]]></category>
		<category><![CDATA[sniff]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[tests]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=254</guid>
		<description><![CDATA[Speed is addictive. After speeding up PHP Code Sniffer runs, the slowest job for Etsy was running php -l on all the files. So, in short, the latest release of CSRunner, version 0.2.1, will execute lint on the recently changed files. You can also run the lint command separately, but why would you want to [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2012/02/new-addition-to-csrunner-php-l/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Thoughts on Accessibility with Regards to Testing</title>
		<link>http://elblinkin.info/2012/02/thoughts-on-accessibility-with-regards-to-testing/</link>
		<comments>http://elblinkin.info/2012/02/thoughts-on-accessibility-with-regards-to-testing/#comments</comments>
		<pubDate>Fri, 10 Feb 2012 19:36:16 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[accessibilty]]></category>
		<category><![CDATA[clean code]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PHPUnit]]></category>
		<category><![CDATA[protection]]></category>
		<category><![CDATA[sniff]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[Test Smell]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[tests]]></category>
		<category><![CDATA[unit]]></category>
		<category><![CDATA[unit testing]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=247</guid>
		<description><![CDATA[In Alternative Thoughts on Sniffs for Useless Method Overriding I discussed the discovery of a horrible dance that some developers will do just to test private functions: See a private method you want to test in isolation Upgrade the private to protected Create a child class implementation of this class in the TestCase file Override [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2012/02/thoughts-on-accessibility-with-regards-to-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mockery Test Case for PHPUnit</title>
		<link>http://elblinkin.info/2012/02/mockery-test-case-for-phpunit/</link>
		<comments>http://elblinkin.info/2012/02/mockery-test-case-for-phpunit/#comments</comments>
		<pubDate>Wed, 08 Feb 2012 21:00:29 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[Mock Objects]]></category>
		<category><![CDATA[mockery]]></category>
		<category><![CDATA[mocks]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PHPUnit]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[tests]]></category>
		<category><![CDATA[unit]]></category>
		<category><![CDATA[unit testing]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=242</guid>
		<description><![CDATA[Mockery is a wonderful PHP mock object framework. It reminds me of Mockito for Java. Mockery is far more fluent than MockObjects, the mock object framework packaged with PHPUnit. Mockery and MockObjects can work in the same environment, independent of one another. Since Mockery is a free standing library, it can be used in PHPUnit, [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2012/02/mockery-test-case-for-phpunit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP CodeSniffer for Recently Changed Files</title>
		<link>http://elblinkin.info/2012/02/php-codesniffer-for-recently-changed-files/</link>
		<comments>http://elblinkin.info/2012/02/php-codesniffer-for-recently-changed-files/#comments</comments>
		<pubDate>Wed, 08 Feb 2012 16:15:48 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[clean code]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[phpcs]]></category>
		<category><![CDATA[PHP_CodeSniffer]]></category>
		<category><![CDATA[sniff]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=238</guid>
		<description><![CDATA[At Etsy we have been running PHP_CodeSniffer as part of our pre-commit. When we ran on the entire code base it took at least 5 minutes, which is too slow for the Etsy Continuous Deployment pipeline. Immediately suggestions flew in to only run the sniffs on the changed files, but you can&#8217;t just define the [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2012/02/php-codesniffer-for-recently-changed-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Developer Testing, Not Necessarily TDD&#8230; Revisited</title>
		<link>http://elblinkin.info/2012/02/developer-testing-not-necessarily-tdd-revisited/</link>
		<comments>http://elblinkin.info/2012/02/developer-testing-not-necessarily-tdd-revisited/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 01:11:32 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[developer testing]]></category>
		<category><![CDATA[tdd]]></category>
		<category><![CDATA[test driven development]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[tests]]></category>
		<category><![CDATA[unit testing]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=228</guid>
		<description><![CDATA[In a previous article, I said Test-Driven Development is a possible development workflow that incorporates Developer Testing, but Developer Testing does not necessarily only exist in Test-Driven Development (TDD). Later I pulled together this graphic I could equate all of the steps between TDD and Waterfall, but would gloss over the design phase. Then, one [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2012/02/developer-testing-not-necessarily-tdd-revisited/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Code Snippet:  Find Files Without Test Files</title>
		<link>http://elblinkin.info/2011/12/code-snippet-find-files-without-test-files/</link>
		<comments>http://elblinkin.info/2011/12/code-snippet-find-files-without-test-files/#comments</comments>
		<pubDate>Tue, 06 Dec 2011 20:53:27 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[developer testing]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PHPUnit]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[test driven development]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[unit]]></category>
		<category><![CDATA[unit testing]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=222</guid>
		<description><![CDATA[I am working on a green-field project and wanted to make sure I roughly knew what was and wasn&#8217;t tested. Sometimes I just simply forget whether or not I wrote a test for a new code file. So I share with you a tiny little script that will list all the files in your source [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2011/12/code-snippet-find-files-without-test-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An Example: Avoid Private Functions in Unit Tests</title>
		<link>http://elblinkin.info/2011/11/an-example-avoid-private-functions-in-unit-tests/</link>
		<comments>http://elblinkin.info/2011/11/an-example-avoid-private-functions-in-unit-tests/#comments</comments>
		<pubDate>Mon, 07 Nov 2011 20:57:53 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PHPUnit]]></category>
		<category><![CDATA[PHP_CodeSniffer]]></category>
		<category><![CDATA[Test Smell]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[unit]]></category>
		<category><![CDATA[unit testing]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=202</guid>
		<description><![CDATA[@__edorian writes: @elblinkin I can&#8217;t seem to make the BowlingGameTest fit your coding standard: [gist here] How does that work out for you? Here is the code he was talking about: &#60;?php class GameTest extends PHPUnit_Framework_TestCase { /** * @var Game */ private $game; protected function setUp() { $this-&#62;game = new Game(); } public function [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2011/11/an-example-avoid-private-functions-in-unit-tests/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Developer Testing, Not Necessarily TDD</title>
		<link>http://elblinkin.info/2011/11/developer-testing-not-necessarily-tdd/</link>
		<comments>http://elblinkin.info/2011/11/developer-testing-not-necessarily-tdd/#comments</comments>
		<pubDate>Fri, 04 Nov 2011 23:58:35 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[developer testing]]></category>
		<category><![CDATA[tdd]]></category>
		<category><![CDATA[test driven development]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[tests]]></category>
		<category><![CDATA[unit testing]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=200</guid>
		<description><![CDATA[During most of my tenure at Google, I taught the Developer Testing course to nearly all the engineering nooglers in the NYC office, and as well as some other east coast offices and engineers visiting from Australia. At Etsy, I spend a fair amount of time actually thinking about developer testing in addition to developer [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2011/11/developer-testing-not-necessarily-tdd/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>PHPUnit Coding Standard: Control Structures</title>
		<link>http://elblinkin.info/2011/11/phpunit-coding-standard-control-structures/</link>
		<comments>http://elblinkin.info/2011/11/phpunit-coding-standard-control-structures/#comments</comments>
		<pubDate>Wed, 02 Nov 2011 16:38:17 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[phpcs]]></category>
		<category><![CDATA[PHPUnit]]></category>
		<category><![CDATA[PHP_CodeSniffer]]></category>
		<category><![CDATA[sniff]]></category>
		<category><![CDATA[Test Smell]]></category>
		<category><![CDATA[unit]]></category>
		<category><![CDATA[unit testing]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=194</guid>
		<description><![CDATA[Finally, on to Control Structures. This should be short and simple. In a unit test there should be absolutely no control structures. Unit tests are meant to minimize your debug time by being small to the point tests on small specific pieces of code. Typically there will be one Test_Case class per production class which [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2011/11/phpunit-coding-standard-control-structures/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHPUnit Coding Standard: Functions</title>
		<link>http://elblinkin.info/2011/10/phpunit-coding-standard-functions/</link>
		<comments>http://elblinkin.info/2011/10/phpunit-coding-standard-functions/#comments</comments>
		<pubDate>Mon, 31 Oct 2011 14:48:09 +0000</pubDate>
		<dc:creator>elblinkin</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[phpcs]]></category>
		<category><![CDATA[PHPUnit]]></category>
		<category><![CDATA[PHP_CodeSniffer]]></category>
		<category><![CDATA[sniff]]></category>
		<category><![CDATA[Test Smell]]></category>
		<category><![CDATA[unit]]></category>
		<category><![CDATA[unit testing]]></category>

		<guid isPermaLink="false">http://elblinkin.info/?p=183</guid>
		<description><![CDATA[Now to talk about Functions. This could arguably be more controversial than the Naming and Classes standards. There will be times where you raise your hand and cry out, &#8220;but that violates DRY principles!&#8221; or &#8220;the xUnit pattern book says this!&#8221; I assure you, I will provide further argument in later articles as none of [...]]]></description>
		<wfw:commentRss>http://elblinkin.info/2011/10/phpunit-coding-standard-functions/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

