News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Padraic Brady's Blog:
Unit Testing One Test, One Assertion - Why It Works
February 17, 2009 @ 07:56:09

Padraic Brady has pormoted simplicity for unit testing in his latest blog post. He suggests that, for each test in your suite, you have only one assertion inside.

Obviously, a ratio of 1:1 would be perfect - but I'm sure we can accept some multiple assertions within a tolerance level. A ratio of more than 1.1:1 would indicate creeping obscurity (a signal it's time for me to intervene, refactor, and do some mutation testing for extra assurance). A ratio of 2:1 indicates a lost cause.

He notes that it probably sounds like a bad idea from the start, but he reinforces the suggestion with a bit of reasoning:

It's this notion of complexity that is often used to justify multiple assertions - if you break it down into the simple components that that complexity was built out of, multiple assertions don't have a leg to stand on (just the rare instances out of your control because they absolutely must be done).

You can see response that's been posted over on the PHP in Action blog in response to Padraic's thoughts.

1 comment voice your opinion now!
unittest assertion test reason opinion multiple phpunit tdd testdrivendesign


blog comments powered by Disqus

Similar Posts

PHPImpact Blog: PHP: Spaghetti alla Bolognese

Matt Frost: Mocking SoapClient

Mike Lively's Blog: YAML Now Supported by PHPUnit Database Extension

thePHP.cc: PHPUnit 4.5 and Prophecy

Debuggable Blog: Running Tests from The Commandline in CakePHP


Community Events

Don't see your event here?
Let us know!


podcast laravel performance example application opinion api community release part2 series introduction configure interview library framework conference voicesoftheelephpant php7 symfony2

All content copyright, 2015 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework