PHPUnit has a built-in method to test if an expected exception occurred during a test case:
$this->setExpectedException('Exception');
You cannot however test the message of the exception. There are cases where a program may throw the same exception type, but with different messages for different errors, and you want to differentiate between them.
Here is my example code on how to reliably test for the type and message of an exception:
class staticSessionTest extends PHPUnit_Framework_TestCase { ... function test_bad_data() { $emess = null; try { $this->sess->start('must be array', FALSE, FALSE); # we expect an Exception here } catch (Exception $e) { $emess = $e->getMessage(); } $this->assertEquals($emess, 'Session data must be an array'); } ... }
Putting the assertEquals() outside of the try…catch block ensures that you cannot forget to test for the message. The type of the exception is coded inside the catch(…) block.
UPDATE: I just re-read the latest PHPUnit Annotations, and this feature is already included in the standard PHPUnit suite. The difference between my custom code and the “@expectedExceptionMessage” annotation is that the annotation is valid for the whole test block of execution, while using try…catch you can specify precisely where you expect the exception to occur.
References:
February 13, 2013 at 11:36 pm
Your article helped me avoid writing extra code.
@expectedExceptionMessage annotation came handy and helped a lot.
Thanks for the artilce.
February 15, 2013 at 9:53 am
You’re welcome. 🙂