I\'ve heard the phrase \"deploying applications\" which sounds much better/easier/more reliable than uploading individual changed files to a server, but I don\'t know where
Automatic deploy + run of tests to a staging server is known as continuous integration. The idea is that if you check in something that breaks the tests, you would get notified right away. For PHP, you might want to look into Xinc or phpUnderControl
You'd generally not want to automatically deploy to production though. The normal thing to do is to write some scripts that automates the task, but that you still need to manually initiate. You can use frameworks such as Phing or other build-tools for this (A popular choice is Capistrano), but you can also just whisk a few shell-scripts together. Personally I prefer the latter.
The scripts themselves could do different things, depending on your application and setup, but a typical process would be:
svn export svn://path/to/repository/tags/RELEASE_VERSION /usr/local/application/releases/TIMESTAMPunlink /usr/local/application/current && ln -s /usr/local/application/releases/TIMESTAMP /usr/local/application/currentln -s /usr/local/application/var /usr/local/application/releases/TIMESTAMP/var/usr/local/application/current/scripts/migrate.php(Assuming you have your application in /usr/local/application/current)