<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 06:02:26 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Chris Hartjes' Blog: Tricorder: A Testing Helper for PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/18036</guid>
      <link>http://www.phpdeveloper.org/news/18036</link>
      <description><![CDATA[<p>
<i>Chris Hartjes</i>, a big proponent of testing in the PHP community, has a new post to his blog about <a href="http://www.littlehart.net/atthekeyboard/2012/05/31/tricorder-a-testing-helper-for-php/">a new testing tool</a> he's released to make it easier for you to know what needs testing - <a href="https://github.com/chartjes/php-tricorder/">Tricorder</a>.
</p>
<blockquote>
I've hacked together a little CLI script that I think will be of use to many people who are trying to answer the question "just what should I do to test this thing anyway?" as they learn how to write PHPUnit tests to go along with their code. [...] I've created something that I am calling <a href="https://github.com/chartjes/php-tricorder/">PHP-Tricorder</a>, a CLI utility that can be used in conjunction with phpdoc structure.xml files to make suggestions on testing scenarios. It's at a 0.1 release right now, so I anticipate it will grow and add more features as time goes on.
</blockquote>
<p>
The post includes an example of the output generated from the <a href="http://phpdoc.org/">phpdoc</a>'s XML output, recommending things like:
</p>
<ul>
<li>Mocking certain objects
<li>Testing for data types and contents
<li>Recommending testing ideas for private/protected methods
</ul>
<p>
You can grab (or contribute to!) the latest version of the tool <a href="https://github.com/chartjes/php-tricorder/">over on github</a>.
</p>]]></description>
      <pubDate>Fri, 01 Jun 2012 11:11:15 -0500</pubDate>
    </item>
  </channel>
</rss>
