<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
				<title>Comments on: Unit Tests: How to test for Exceptions</title>
		<link>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html</link>
		<description>Unit Tests: How to test for Exceptions Comment Feed</description>
				<language>de</language>
		<pubDate>Thu, 09 Sep 2010 20:35:11 +0000</pubDate>
		<generator>mcw[blog] 'Ruby' Alpha 3</generator>
		<item>
			<title>Comment #1 by: Dagfinn Reiersøl</title>
			<link>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment947</link>
			<guid>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment947</guid>
			<author>Dagfinn Reiersøl</author>			
			<pubDate>Tue, 21 Apr 2009 10:53:06 +0000</pubDate>
			<content:encoded><![CDATA[ It's good to know this way of doing it, but the PHP test frameworks have features specifically for testing exceptions. SimpleTest (which seems to be the one in use here) has an expectException() method. (See http://forums.devnetwork.net/viewtopic.php?p=369062). PHPUnit has an @expectedException annotation. ]]></content:encoded>
		</item>
		<item>
			<title>Comment #2 by: Geoffray</title>
			<link>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment955</link>
			<guid>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment955</guid>
			<author>Geoffray</author>			
			<pubDate>Wed, 22 Apr 2009 11:30:33 +0000</pubDate>
			<content:encoded><![CDATA[ My comment will probably not change the world, but in your last example, shouldn't it be more logic if you also put the unset() back into the catch block ?<br />
<br />
Regards ]]></content:encoded>
		</item>
		<item>
			<title>Comment #3 by: Dominik Jungowski</title>
			<link>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment959</link>
			<guid>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment959</guid>
			<author>Dominik Jungowski</author>			
			<pubDate>Wed, 22 Apr 2009 21:12:45 +0000</pubDate>
			<content:encoded><![CDATA[ You're absolutely right! I just changed it, thank you :) ]]></content:encoded>
		</item>
		<item>
			<title>Comment #4 by: templerel</title>
			<link>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment7299</link>
			<guid>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment7299</guid>
			<author>templerel</author>			
			<pubDate>Sat, 14 Nov 2009 10:27:18 +0000</pubDate>
			<content:encoded><![CDATA[ Thank you for a very instructive article ]]></content:encoded>
		</item>
		<item>
			<title>Comment #5 by: kefAgifFkeX</title>
			<link>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment8316</link>
			<guid>http://www.phpdevblog.net/2009/04/unit-tests-how-to-test-for-exceptions.html#comment8316</guid>
			<author>kefAgifFkeX</author>			
			<pubDate>Mon, 07 Dec 2009 01:24:49 +0000</pubDate>
			<content:encoded><![CDATA[ I don't know If I said it already but &#8230;Great site&#8230;keep up the good work. :) I read a lot of blogs on a daily basis and for the most part, people lack substance but, I just wanted to make a quick comment to say I'm glad I found your blog.  Thanks, :)<br />
<br />
A definite great read.. ]]></content:encoded>
		</item>
		</channel>
</rss>