<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/user/kasi77/marks/tag/unit testing">
<title>Public marks from user kasi77 with tag &quot;unit testing&quot;</title>
<description>Public marks from user kasi77 with tag &quot;unit testing&quot;</description>
<link>http://blogmarks.net/user/kasi77/marks/tag/unit testing</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1057866324"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1057866324">
<title>i should be coding :: unit tests and code coverage with phpt</title>
<link>http://ishouldbecoding.com/2008/05/23/unit-tests-and-code-coverage-with-phpt</link>
<description>My initial experiences with unit testing and PHP were with PHPUnit. While it's a great tool and I have to give kudos to Sebastian for contributing so much to its development, I've come to appreciate the simplicity of PHPT tests. Recently, I wrote some for a project and realized that I wasn't aware of how to generate code coverage reports. Many thanks to the very helpful patrons in the #pear channel on EFNet for helping me to get this working.</description>
<dc:date>2008-06-02T16:53:33Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>php, code, coverage, unit testing</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://ishouldbecoding.com/2008/05/23/unit-tests-and-code-coverage-with-phpt"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://ishouldbecoding.com/2008/05/23/unit-tests-and-code-coverage-with-phpt">i should be coding :: unit tests and code coverage with phpt</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
<p class="description">My initial experiences with unit testing and PHP were with PHPUnit. While it's a great tool and I have to give kudos to Sebastian for contributing so much to its development, I've come to appreciate the simplicity of PHPT tests. Recently, I wrote some for a project and realized that I wasn't aware of how to generate code coverage reports. Many thanks to the very helpful patrons in the #pear channel on EFNet for helping me to get this working.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/coverage">coverage</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unit%2Btesting">unit testing</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057866324">Copy</a> | 
<a href="http://blogmarks.net/link/2800052">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>