News Feed
Sections




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

PHP in Action Blog:
One behavior != one assertion
February 24, 2009 @ 11:13:17

On the PHP in Action blog, despite some agreement with Padraic Brady on his one behavior, one assertion method for writing unit tests, Dagfinn Reiersol still has his reservations.

Pádraic maintains that one assertion per test is a rule that should always be followed unless there is a specific good reason to break it. I prefer it as a guideline, as does Robert C. Martin in the book Clean Code. The reference is not intended as an appeal to authority to "prove" that I'm right. I'm just making the point that I think this reflects the current state of the art, which is not necessarily perfect, of course.

Dagfinn talks about behavior-driven development and illustrates how a two assertions could be combined into one but that the end result "isn't very pretty" - and that's just testing two proterties of a single object. Imagine what would happen if things got more complex.

0 comments voice your opinion now!
unittest behavior assertion reservation opinion padraicbrady


blog comments powered by Disqus

Similar Posts

Reddit.com: PHP now, as an outdated developer

Anna Filina's Blog: Developer Community: Where to Start? – Part 1

Mike Lively's Blog: Why I Hate Singletons

Reddit.com: Frameworks, is the learning curve too steep

Marco Tabini's Blog: The easiest way to add unit test to your application


Community Events





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


artisanfiles introduction laravel tool community opinion voicesoftheelephpant language interview security series list composer library version release symfony podcast framework conference

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