Here are some ideas I was thinking of for making testing Zend Framework (and Doctrine) based apps nice and easy.
Testing library code should be relatively simple, since most of it probably works more like “traditional” code: It does not output html, does not access the DB and things like that.
Testing models and controllers is a more complex thing. Models quite likely will access the DB, so how to make testing them simpler?
First, you could use the in-memory SQLite adapter with PDO (new PDO(‘sqlite::memory:’)) to create a database that won’t mess with anything external. Then, if you’re using a library like Doctrine, you can let it generate the database for you based on the models. You would also want to write some fixtures with some dummy data that you can use in your tests.
Since Doctrine’s models should work most of the time, you may not want to spend time writing tests for them, but if you provide any custom methods in your models, you might want to make sure they do what they are supposed to.
Controller testing can be the most difficult part, and this is where you may need to perform some refactoring if your design is not suitable for testing. For example, you may have a lot of logic in your controllers, which might be better off in your models or library code. Testing the whole idea of getting out the correct output or redirects may be difficult, but the Zend Framework test case stuff Matthew Weier O’Phinney has been working on should help a lot there.
In addition to testing the stuff that happens on the server, you may want to test what’s actually going on on the client side of things.