Sebastian Bergmann has posted a reminder for his upcoming PHPUnit workshops happening in Melbourne, Australia (Aug 4th-6th) and in Brisbane (Aug 11th-12th and 14th).

A few seats are still available for both of these workshops. Secure your seat today! I am also available for in-house training, coaching, and consulting around the days of the workshops.

You can save your spot for one of these events by visiting this page and entering you info (you'll want the "Quality Assurance in PHP Projects" option).

Brian DeShong has posted some of his "food for thought" on the development process that's behind the scenes of different PHP applications.

Lately I've been doing a lot of thinking on development processes and quality, specifically for large-scale, professional PHP-based projects. [...] Generally speaking, my perception is that software development shops that really care about and emphasize quality have processes that consist of things such as writing use cases, unit testing and continuous integration.

He knows how he feels about all of this, be he wants to hear back from the community. How far does quality assurance go in your group? What kind of time/funding does this involve? Leave him a comment and let him know...

Lukas Smith looks, in a new post today, asking for some of the current thoughts and feelings surrounding the process of QA-ing PHP applications.

He goes through five different steps in a QA process that can help you find the issues with your application long before any user gets their hands on it:

• using testing tools like PHPUnit or phpt (including code coverage
• moving on to Selenium or BadBoy (or similar testing tools) to check the runtime flow
• making ample documentation with things like phpDocumentor or Doxygen
• Providing debugging tools for frameworks to make locating errors easier than digging through code and comments
• use code analyzers to check for attacks/vulnerabilities like cross-site scripting or SQL injections

So what am I missing? Any tool I should have mentioned, team management approach? I am sure I have since I just wrote this blog post very quickly and I do not have a check list yet. Speaking of checklist, that sounds like a good thing to have when doing QA.