Script Testing

[squidsk]

Originally Posted by jagtpf

Funnily enough some things that don't work on the test site, work on the live (and vice versa).

This will usually be caused by the fact that your test site is not identical to your live site, including but not limited to, php version/settings, mysql version/settings, vb version/settings, installed mods verion/settings, data on your live site is different from your test site, and a host of others as well.

But some long scripts that involve a lot of actions, how do you keep track? It seems inefficient to play guessing at least some of the time and not to be able to use a good php/xml editor/diagnostic to check.

You write extra code, that you remove later, which outputs running data either to the screen or to a file on the server which you can review to determine how far you got, or like vbulletin upgrades you have steps and and you output stuff before and after each step to be able to figure out where things went wrong if they do wrong. If doing this last one, make sure each step is small so that figuring what is wrong to fix it only has to look at a few different things. The bigger each step is the more complex it is to debug the step.