updates: identi.ca, twitter

="sydphp"

Sydney PHP Group provides a community for PHP developers in Sydney, Australia.
We run regular meetings in the city and membership is free and open to anyone with an interest in web development.

How do I join?

Register an account on our blog

What next?

After registration, you can RSVP one or more attendees for events. If you wish to present, come to a meeting and have a chat with a group organiser.

Who are the organisers?

Currently Tim, James, Graham and Dean. One or more of us will be attending each meeting and you can reach us by DM'ing sydphp on Twitter

Get yourself known!

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

Current Events

View and RSVP to current events

Subscribe to the one-way announcement mailing list at Google Groups for updates.

PHP Jobs in Sydney

We a provide a free, one-way mailing list at Google Groups. Posts are moderated before being published.

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