News Feed
Jobs 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

Content with Style: Getting phpunit to work with MAMP

User Group: Boston PHP Welcomes Chris Shiflett

Keith Casey's Blog: Bad Assumptions in Development

J-P Stacy: Neither developers nor the language are what's wrong with PHP

Artur Ejsmont's Blog: A few words on bugs and software quality


Community Events











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


overview composer podcast performance hack release facebook install framework hhvm security symfony2 unittest component package application opinion introduction language database

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