<?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/marks/tag/unit testing">
<title>Public marks with tag &quot;unit testing&quot;</title>
<description>Public marks with tag &quot;unit testing&quot;</description>
<link>http://blogmarks.net/marks/tag/unit testing</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/mfaure/mark/1058576555"/>
<rdf:li resource="http://blogmarks.net/api/user/Xavier Lacot/mark/1058176378"/>
<rdf:li resource="http://blogmarks.net/api/user/Xavier Lacot/mark/1058132831"/>
<rdf:li resource="http://blogmarks.net/api/user/Xavier Lacot/mark/1057969520"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1057866324"/>
<rdf:li resource="http://blogmarks.net/api/user/mbertier/mark/1057544866"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1057469902"/>
<rdf:li resource="http://blogmarks.net/api/user/roulian/mark/1780118"/>
<rdf:li resource="http://blogmarks.net/api/user/roulian/mark/1714812"/>
<rdf:li resource="http://blogmarks.net/api/user/mbertier/mark/1288209"/>
<rdf:li resource="http://blogmarks.net/api/user/mbertier/mark/1152718"/>
<rdf:li resource="http://blogmarks.net/api/user/sledge/mark/325532"/>
<rdf:li resource="http://blogmarks.net/api/user/mbertier/mark/6145"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/mfaure/mark/1058576555">
<title>HowToWriteHardToTestCode.pdf - Google Docs</title>
<link>https://docs.google.com/fileview?id=0B7z6S2TvsDWSYWQ1NGEwOTctYTEwOS00ZTUwLWE2Y2QtZjEwMmE2OTQzNjVh&amp;hl=en</link>
<description></description>
<dc:date>2009-11-09T16:42:03Z</dc:date>
<dc:author>mfaure</dc:author>
<dc:subject>google, unit testing, test unitaire</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="https://docs.google.com/fileview?id=0B7z6S2TvsDWSYWQ1NGEwOTctYTEwOS00ZTUwLWE2Y2QtZjEwMmE2OTQzNjVh&amp;hl=en"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="https://docs.google.com/fileview?id=0B7z6S2TvsDWSYWQ1NGEwOTctYTEwOS00ZTUwLWE2Y2QtZjEwMmE2OTQzNjVh&amp;hl=en">HowToWriteHardToTestCode.pdf - Google Docs</a></h4>
 
by <a href="http://blogmarks.net/user/mfaure">mfaure</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unit%2Btesting">unit testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/test%2Bunitaire">test unitaire</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058576555">Copy</a> | 
<a href="http://blogmarks.net/link/3404201">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Xavier Lacot/mark/1058176378">
<title>Functional Test Generation with symfony 1.2 - Thomas Rabaix</title>
<link>http://rabaix.net/en/articles/2009/01/27/functional-test-generation-with-symfony-1-2</link>
<description>A nice &quot;click-and-browse&quot; way to create functionnal tests with Symfony 1.2.</description>
<dc:date>2009-01-29T23:36:12Z</dc:date>
<dc:author>Xavier Lacot</dc:author>
<dc:subject>symfony, test, unit testing, 1.2, plugin, functionnal testing</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://rabaix.net/en/articles/2009/01/27/functional-test-generation-with-symfony-1-2"><img border="0" src="http://blogmarks.net/screenshots/2009/01/29/0b2f0876ab895db1c92b66efd13db308.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://rabaix.net/en/articles/2009/01/27/functional-test-generation-with-symfony-1-2">Functional Test Generation with symfony 1.2 - Thomas Rabaix</a></h4>
 
by <a href="http://blogmarks.net/user/Xavier Lacot">Xavier Lacot</a> 
<p class="description">A nice "click-and-browse" way to create functionnal tests with Symfony 1.2.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/symfony">symfony</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/test">test</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unit%2Btesting">unit testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/1.2">1.2</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/plugin">plugin</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/functionnal%2Btesting">functionnal testing</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058176378">Copy</a> | 
<a href="http://blogmarks.net/link/3070242">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Xavier Lacot/mark/1058132831">
<title>FireUnit: Firebug Unit Testing for Firefox</title>
<link>http://fireunit.org/</link>
<description>A firefox firebug extension for javascript unit testing</description>
<dc:date>2008-12-18T14:51:44Z</dc:date>
<dc:author>Xavier Lacot</dc:author>
<dc:subject>firefox, firebug, javascript, unit testing, test</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://fireunit.org/"><img border="0" src="http://blogmarks.net/screenshots/2008/12/18/f09e456465577b858e601e775cbe2f8e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://fireunit.org/">FireUnit: Firebug Unit Testing for Firefox</a></h4>
 
by <a href="http://blogmarks.net/user/Xavier Lacot">Xavier Lacot</a> 
<p class="description">A firefox firebug extension for javascript unit testing</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firefox">firefox</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firebug">firebug</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unit%2Btesting">unit testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/test">test</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058132831">Copy</a> | 
<a href="http://blogmarks.net/link/3033197">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Xavier Lacot/mark/1057969520">
<title>Vitamin Features » Easy Automated Web Application Testing with Hudson and Selenium</title>
<link>http://www.thinkvitamin.com/features/webapps/easy-automated-web-application-testing-with-hudson-and-selenium</link>
<description>Developing web applications is getting more complex - it’s easy to accidentally break functionality as changes are made. In this article, Ben describes the setup his team uses test their apps as changes are committed; automatically notifying the developers of any problems.</description>
<dc:date>2008-09-02T13:55:07Z</dc:date>
<dc:author>Xavier Lacot</dc:author>
<dc:subject>web, test, uat, selenium, hudson, unit testing</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.thinkvitamin.com/features/webapps/easy-automated-web-application-testing-with-hudson-and-selenium"><img border="0" src="http://blogmarks.net/screenshots/2008/09/03/f50d98ed88c39123149fdcbf62a70331.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.thinkvitamin.com/features/webapps/easy-automated-web-application-testing-with-hudson-and-selenium">Vitamin Features » Easy Automated Web Application Testing with Hudson and Selenium</a></h4>
 
by <a href="http://blogmarks.net/user/Xavier Lacot">Xavier Lacot</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2887622">3 other(s)</a> 
<p class="description">Developing web applications is getting more complex - it’s easy to accidentally break functionality as changes are made. In this article, Ben describes the setup his team uses test their apps as changes are committed; automatically notifying the developers of any problems.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/test">test</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/uat">uat</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/selenium">selenium</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hudson">hudson</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=1057969520">Copy</a> | 
<a href="http://blogmarks.net/link/2887622">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <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> <item rdf:about="http://blogmarks.net/api/user/mbertier/mark/1057544866">
<title>Google Testing Blog: Automating tests vs. test-automation</title>
<link>http://googletesting.blogspot.com/2007/10/automating-tests-vs-test-automation.html</link>
<description>The common attitude, that the UI deserves most attention because it is what the user sees, is flawed. Even a perfect UI will not satisfy a user if the underlying functionality is corrupt.</description>
<dc:date>2007-11-13T10:51:50Z</dc:date>
<dc:author>mbertier</dc:author>
<dc:subject>clevermarks, unit testing, ui</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://googletesting.blogspot.com/2007/10/automating-tests-vs-test-automation.html"><img border="0" src="http://blogmarks.net/screenshots/2007/11/13/ec71364564f5423388736e203cac57f2.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://googletesting.blogspot.com/2007/10/automating-tests-vs-test-automation.html">Google Testing Blog: Automating tests vs. test-automation</a></h4>
 
by <a href="http://blogmarks.net/user/mbertier">mbertier</a> 
<p class="description">The common attitude, that the UI deserves most attention because it is what the user sees, is flawed. Even a perfect UI will not satisfy a user if the underlying functionality is corrupt.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/clevermarks">clevermarks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unit%2Btesting">unit testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ui">ui</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057544866">Copy</a> | 
<a href="http://blogmarks.net/link/2531827">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1057469902">
<title>Perl testing reference card</title>
<link>http://langworth.com/pages/perltestref</link>
<description></description>
<dc:date>2007-10-04T13:39:45Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>reference, perl, unit testing</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://langworth.com/pages/perltestref"><img border="0" src="http://blogmarks.net/screenshots/2007/10/04/e1fec8e137da26dad580a2583d9fc103.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://langworth.com/pages/perltestref">Perl testing reference card</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/reference">reference</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/perl">perl</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=1057469902">Copy</a> | 
<a href="http://blogmarks.net/link/2465528">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/roulian/mark/1780118">
<title>La boite à outils du programmeur Java</title>
<link>http://java.developpez.com/outils/developpeur/</link>
<description>Une liste d'outils pour bien développer en Java.</description>
<dc:date>2007-01-16T21:23:46Z</dc:date>
<dc:author>roulian</dc:author>
<dc:subject>java, api, unit testing, application_server, web services, database</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://java.developpez.com/outils/developpeur/"><img border="0" src="http://blogmarks.net/screenshots/2007/01/16/11940c6b701faab2cb57f85d891b9101.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://java.developpez.com/outils/developpeur/">La boite à outils du programmeur Java</a></h4>
 
by <a href="http://blogmarks.net/user/roulian">roulian</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/299746">1 other(s)</a> 
<p class="description">Une liste d'outils pour bien développer en Java.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/java">java</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unit%2Btesting">unit testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/application_server">application_server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web%2Bservices">web services</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/database">database</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1780118">Copy</a> | 
<a href="http://blogmarks.net/link/299746">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/roulian/mark/1714812">
<title>Jakarta Cactus</title>
<link>http://jakarta.apache.org/cactus/index.html</link>
<description> Cactus is a simple test framework for unit testing server-side java code (Servlets, EJBs, Tag Libs, Filters, ...).
The intent of Cactus is to lower the cost of writing tests for server-side code. It uses JUnit and extends it.
Cactus implements an in-container strategy, meaning that tests are executed inside the container. </description>
<dc:date>2007-01-08T14:10:32Z</dc:date>
<dc:author>roulian</dc:author>
<dc:subject>unit testing, java</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://jakarta.apache.org/cactus/index.html"><img border="0" src="http://blogmarks.net/screenshots/2007/01/08/7f99ea3e71f2f40037cae09ab5d2fa8b.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://jakarta.apache.org/cactus/index.html">Jakarta Cactus</a></h4>
 
by <a href="http://blogmarks.net/user/roulian">roulian</a> 
<p class="description"> Cactus is a simple test framework for unit testing server-side java code (Servlets, EJBs, Tag Libs, Filters, ...).
The intent of Cactus is to lower the cost of writing tests for server-side code. It uses JUnit and extends it.
Cactus implements an in-container strategy, meaning that tests are executed inside the container. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unit%2Btesting">unit testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/java">java</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1714812">Copy</a> | 
<a href="http://blogmarks.net/link/1456537">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mbertier/mark/1288209">
<title>Advanced Unit Test, Part V - Unit Test Patterns - The Code Project - Design and Strategy</title>
<link>http://www.codeproject.com/gen/design/autp5.asp</link>
<description></description>
<dc:date>2006-11-30T14:37:51Z</dc:date>
<dc:author>mbertier</dc:author>
<dc:subject>dev, unit testing, bestpractices</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.codeproject.com/gen/design/autp5.asp"><img border="0" src="http://blogmarks.net/screenshots/2006/12/02/d70b3c1539787e780f20237d688f7365.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.codeproject.com/gen/design/autp5.asp">Advanced Unit Test, Part V - Unit Test Patterns - The Code Project - Design and Strategy</a></h4>
 
by <a href="http://blogmarks.net/user/mbertier">mbertier</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1038430">2 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dev">dev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unit%2Btesting">unit testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bestpractices">bestpractices</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1288209">Copy</a> | 
<a href="http://blogmarks.net/link/1038430">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mbertier/mark/1152718">
<title>Projects:phpcoverage - Spike Developer Zone</title>
<link>http://developer.spikesource.com/wiki/index.php/Projects:phpcoverage</link>
<description>Spike PHPCoverage is an open-source tool for measuring and reporting code coverage provided by the test suite of a PHP application. Spike PHPCoverage can instrument and record the line coverage information for any PHP script at runtime</description>
<dc:date>2006-10-27T14:28:24Z</dc:date>
<dc:author>mbertier</dc:author>
<dc:subject>php, unit testing, tools</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://developer.spikesource.com/wiki/index.php/Projects:phpcoverage"><img border="0" src="http://blogmarks.net/screenshots/2007/01/02/0c3c4689f30b938c9fd5b4a856cfb66e.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://developer.spikesource.com/wiki/index.php/Projects:phpcoverage">Projects:phpcoverage - Spike Developer Zone</a></h4>
 
by <a href="http://blogmarks.net/user/mbertier">mbertier</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/906009">2 other(s)</a> 
<p class="description">Spike PHPCoverage is an open-source tool for measuring and reporting code coverage provided by the test suite of a PHP application. Spike PHPCoverage can instrument and record the line coverage information for any PHP script at runtime</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/unit%2Btesting">unit testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1152718">Copy</a> | 
<a href="http://blogmarks.net/link/906009">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/sledge/mark/325532">
<title>Hands on with ASTUce in JavaScript</title>
<link>http://www.zwetan.com/blog/buRRRn/ASTUce/Hands_on_with_ASTUce_in_JavaScript.html</link>
<description>Here is a very simple tutorial to get you started with ASTUce and unit testing.</description>
<dc:date>2006-01-27T17:07:25Z</dc:date>
<dc:author>sledge</dc:author>
<dc:subject>javascript, tutorial, unit testing</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.zwetan.com/blog/buRRRn/ASTUce/Hands_on_with_ASTUce_in_JavaScript.html"><img border="0" src="http://www.blogmarks.net/screenshots/2006/01/27/a2b64adc9e0d59d84436f1c5864be46d.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.zwetan.com/blog/buRRRn/ASTUce/Hands_on_with_ASTUce_in_JavaScript.html">Hands on with ASTUce in JavaScript</a></h4>
 
by <a href="http://blogmarks.net/user/sledge">sledge</a> 
<p class="description">Here is a very simple tutorial to get you started with ASTUce and unit testing.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorial">tutorial</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=325532">Copy</a> | 
<a href="http://blogmarks.net/link/493986">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mbertier/mark/6145">
<title>Tutoriel SimpleTest : découvrir les tests unitaires - :: onpk :: blog PHP, MySQL, développement web &amp; connexe(s)</title>
<link>http://www.onpk.net/index.php/2005/01/12/254-tutoriel-simpletest-decouvrir-les-tests-unitaires</link>
<description></description>
<dc:date>2005-01-13T09:07:05Z</dc:date>
<dc:author>mbertier</dc:author>
<dc:subject>php, dev, tutorial, unit testing</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.onpk.net/index.php/2005/01/12/254-tutoriel-simpletest-decouvrir-les-tests-unitaires"><img border="0" src="http://www.blogmarks.net/screenshots/2005/01/13/f8c8a1ce197862103f6531487fba6c88.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.onpk.net/index.php/2005/01/12/254-tutoriel-simpletest-decouvrir-les-tests-unitaires">Tutoriel SimpleTest : découvrir les tests unitaires - :: onpk :: blog PHP, MySQL, développement web &amp; connexe(s)</a></h4>
 
by <a href="http://blogmarks.net/user/mbertier">mbertier</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2480">1 other(s)</a> 
<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/dev">dev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorial">tutorial</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=6145">Copy</a> | 
<a href="http://blogmarks.net/link/2480">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>