sorry i commented in all the wrong places :| Edmund Hertle wrote:
By locally created and tested scripts you will of course not have those probs because you're not comitting everything. But locally developing brings some kind of care-taking like making sure you use everywhere the same version (php, mysql, webserver), installed the same extensions, have the same php.ini, than there the whole database... and php is not my main work ;)
you don't have to locally develop, you can develop however you want :) svn is just version controlling all your files to make it easier to team work and to rollback code. you then tag good versions of the code in svn so you have a permanent easy to access good version of the site (which you then copy and do what you want with, download, ftp whatever) keeps you safe :)
it's kind of like taking a zip/backing up the site everytime it's error free - but on steriods.
all those talking was only about the developing server. Unit testing I heard of but not really understand how to use and what excatly unit testing does.
unit testing is where you write tests for each small section of code, say each function or object/method - you write a test so you know the code works, then when you change anything in the code you can run the test again and if it fails.. well you have a bug - way more too it so see: http://en.wikipedia.org/wiki/Unit_testing
I'd recommend: http://www.phpunit.de/ however simply writing tests for your code yourself is a good start - something somewhere on the internet says: "whenever you feel like writing a print_r or var_dump or echo'ing a variable, don't - write a test instead" - not always practical but still good thinking.
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
