For any web developer that's ever had to build a signup routine, email is the necessary evil that takes pride of place among hated activities. Sure, a simple call to the language's mail library will send a message through, but the moment the boss wants a HTML email, or users need attachments, everything starts to get tricky.

They try to solve the mail return issue (it tells if the message has gone to the queue, not been delivered) with a little testing and Fakemail. The software looks for emails based on the configuration given and pulls them out to a local directory. Your script can then look here and check the validity of the message before its sent.

This even allows for integration with things like Phing, SimpleTest and Selenium.

We recently looked at front-end testing of web applications with Selenium. Today, we'll take another approach to testing your PHP applications: backend unit testing for your actual PHP code. As part of our posts on test driven development, here's a quick intro to using SimpleTest to test your PHP applications.

He introduces the SimpleTest software and shows what a sample test might look like for a simple math question (testing to see if the result of the addition is correct). He also points out a good tutorial on the SimpleTest website to help you get started.

Most of us familiar with unit testing with CakePHP and SimpleTest know that SimpleTest always executes all methods starting with the string "test". This can be problematic sometimes. At this point you have two options: create a new testcase, put an "x" before every other test name or use the following tip.

His tip puts another layer on top of the usual testing and uses the getTests method to define with of the tests need to be run. If it's defined, SimpleTest will only execute those.

I came across a Zend Framework (ZF) example I wanted to refactor. You really have to have unit test coverage to refactor effectively, and since there were no tests, I started trying to find out how to test it. There didn't seem to be a wealth of information available on the web, so I've tried to figure it out by myself.

He walks through the testing process he followed - making some new default objects (for SimpleTest) and, using the flash messenger view helper, makes some mock classes to simulate sending the flash messages in an application.

For now over three years we are working with unit tests. I'd like to share some of those experiences. As we have two frameworks in place for our website, I can compare two different strategies for unit tests.

He talks about their choice of SimpleTest, their test monitoring, CruiseControl and their "if it doesn't pass, you can't release it" mentality to keep their site as bug free as possible.

So you want to read up on Unit Testing in CakePHP? That is great, testing can be such a help in finding bugs. [...] Surprisingly, many people do not know yet what unit testing is. In this first part of a whole series you can get a good grasp of what it is and is not.

He goes over the basic concepts behind the testing - setting up test cases, comparing results, automating them and how they related to code coverage. He gets into more detail with a list of the assert functions (like assertNotEqual or assertClone) and some examples using the simpletest unit testing software. He wraps it up by listing some of the benefits of unit testing, the limitations of it, TDD and what Mock objects are.

I just started listing the techniques I've learned when writing tests to exercise the web interface of a PHP application. This is from my experience and my personal preferences; it's not the final word or necessarily right for everyone.

He suggests:

• Use SimpleTest's Web tester if you can
• Test the web output using regular expressions
• Use element IDs or names to test links, forms and fields
• Log HTTP requests in the application

A last day of a month - time to release a new Stubbles version. The release does not feature that much new features, we focused mainly on infrastructure and code quality improvements. The most important change of course is the change of the package separator.

Instead of the dots they've gone with the more standard double-colon that PHP already uses. There were also code quality improvements and a move away from SimpleTest out to the popular PHPUnit unit testing package.

You can download this new package from the Stubbles project site.

As I mentioned in my blog post on Paparrazzi testing, Uncle Bob (Robert C. Martin) has discussed how to test web templates or server pages. Since I'm currently working with Smarty templates, I wanted a simple way to run tests on them without needing to deal with a web server and the page navigation in a full web application.

Thankfully, he's found a nice, simple method for running tests against the Smarty engine (and includes that in the post - an interface to Smarty and the example test case to run against it).

Some minutes ago I released the first version of vfsStream. vfsStream is a stream wrapper for a virtual file system that may be helpful in unit tests to mock the real file system. It can be used with any unit test framework, like PHPUnit or SimpleTest.

The idea for the class came about when he thought about the use of real databases vs test databases and applied it to file systems. You can grab the latest version from their trac website as well as get more information about known issues and a brief example of its use.