updates: identi.ca, twitter

="sydphp"

Sydney PHP Group provides a community for PHP developers in Sydney, Australia.
Membership is free and open to anyone with an interest in web development.

Now aggregating!

Do you provide web development related services in Sydney and want that information available to the Sydney PHP development community? You can reach our community by getting your RSS/ATOM feed syndicated on sydphp.org

How do I join?

Just attend a meeting, present a topic if you wish or add your thoughts to our blog

Search

Mailing List

The group maintains an announcement mailing list at Google Groups, used to notify members of upcoming web development events in the Sydney region

Events Calendar

Subscribe to the sydphp calendar and receive event notifications as they happen

Flickr pool

Unit tests

I just read a post asking if my unit test take too long. In it the author suggests that 5 minutes is long and asks if anyone has solved this problem. This reminded me of a discussion I had with some developers about 12 months ago about unit testing in which my argument was simply that unit tests need to be comprehensive and not necessarily quick.


There are many projects where the unit tests take several hours to run. This shouldn’t matter during development when you’re probably only interested in a few unit tests as most test tools provide a way to filter the tests that are run. You only need to run the entire test suite prior to committing or during continuous integration.


Having said all of that I can recommend using memory tables if your database supports them. The operations are generally a lot faster as the database doesn’t need to write to disk.


Share your thoughts