Bughuntday is a whole day developers can come together to start fixing bugs for open-source frameworks and libraries. This Saturday we started these series with Zend Framework, a hugely adopted PHP framework within enterprise and professional web application development.

He also includes the slides from the presentation and a video of Jurien Stutterheim's talk introducing everyone to testing and the Zend Framework. There's pictures of the event on Flickr too.

Check here for an updated video from the event.

Yesterday was the first BugHuntDay that our dutch PHP usergroup organized together with the Belgian usergroup. Somewhere between 25 and 30 people (I forgot to do an actual headcount) came together in Roosendaal to work on fixing bugs in Zend Framework.

He recounts their arrival (he and their speaker Jurrien), his talk on the structure of the framework and how to test it and some of the bugs that he worked on. Everyone that attended also received an elePHPant for their contributions. Other "goodies" like Zend t-shirts and a coupon for a free Zend Certification Exam we're passed out too.

The Zend Framework Community has delivered another feature-rich release of Zend Framework and I'm extremely proud and happy to see the energy and excitement around this project. The ZF team (Wil Sinclair, Matthew Weier O'Phinney, Ralph Schindler, Alexander Veremyev) along with many others in the ZF community and at Zend, have been doing a superb job and have been working very hard to put this release together.

He mentions the Dojo integration, the updates to the SOAP component, updates to make test-driven development simpler and a reminder about ZendCon08 coming soon that will feature several Zend Framework-centric talks.

One of the unit testing best practices suggests to break dependencies, so you can test each component separately. The first problem that arises when you want to test controllers might be having a tighter control over the HTTP Request and Response objects.

This problem is overcome with the Zend_Test_PHPUnit_ControllerTestCase. The second problem it with calls to external resources (like models/databases or web services). This is the prime focus of the post and seceral blocks of code are included to make a class to emulate the HTTP responses you might get back from the service.

Because the Web "environment" is so diverse and contains so many forms of programmatic content, input validation and sanity checking is the key to Web applications security. This involves both identifying and enforcing the valid domain of every user-definable data element, as well as a sufficient understanding of the source of all data elements to determine what is potentially user definable.

They note that the root of most problems is input validation - most applications either just don't do it or do it poorly. They include a few tips on first security the environment the application is running in (like checking the HEAD/OPTIONS values and ensuring you're only allowing known file extensions and directories). They also mention the insecurity behind HIDDEN form elements and some issues surrounding user authentication.

• Johannes Schluter looking at the actual release
• The PHP 10.0 blog mentioning the impact this new release will have on the language and the web
• and a few tests that Lars Strojny has already run on the release.
• Evert Pot's look at some of the upcoming features of PHP 5.3 (including code)
• Some testing from PHP Freaks
• A note about some testing with the Stubbles framework

You can check out this page on the PHP.net wiki for more information on what's left for the final release and a tentative schedule for the releases in between.

This book is absolutely jam-packed with information useful to the medium-advanced PHP coder. SPL is described over a few chapters, and a quick intro to Zend's MVC framework is provided. Of particular interest to me were the final chapters, to do with certificate-based authentication, and a chapter near the beginning describing the upcoming features of PHP6. Great book - I really enjoyed it.

The review gets into detail on some of the chapters and some of the shortfalls that Kae saw about them. Things like:

• The title says "frameworks" but only one is really discussed (Zend Framework)
• The testing/continuous development sections weren't long enough
• The "web 2.0" section was a little sparse
• The only real web service protocol talked about is SOAP.

Overall, though Kae found the book to be worthy of a place on any developer's shelf.

One of my ongoing projects the past few months has been to create an infrastructure for functional testing of ZF projects using PHPUnit. This past weekend, I made the final commits that make this functionality feature complete.

This new functionality allows you to create stub test case classes, use a Zend_Dom_Query object with CSS selectors/XPath for queries and makes available a special PHPUnit test case that handles the interface between some of the custom functionality (boostrapping, dispatching requests, etc) and PHPUnit.

He includes a sample test case that has assertions for calls to a controller with an action, that a page contains a login form and that a page creates a session and redirects to a profile page.

You can get this functionality from the incubator on the subversion repository for the project.

PHP Vikinger is over again. With about 35 attendees, I would think it was a great success. After opening the event, we figured out which topics people were interested in. After voting for the topics, we came up with a nice couple of topics.

Topics included QA/Testing, web application deployment a look at PHP's document object model functionality and some presentations on Project Zero, the new PHP lexer, eZ Components and database abstraction.

First I think it's important to cover the valuable aspects of the book as that will really drive your decision whether the book is worth a read. If you are new to object oriented programming and basic design patterns you will get a fairly good introduction of how to do both in PHP.

He points out some of his favorite parts of the book - the chapter on exceptions, chapter three covering the Standard PHP library - and some of the things he thought could be improved like the order of the parts of the book (4 should be after 1) and his disappointment in the lack of security/scalability/performance topics.