The process of testing and fixing a website?

[eluser]boltsabre[/eluser]
Well, it depends on how well it's been documented... if you have full documentation (ie, class diagrams, use case flows, etc), it makes your job a lot easier as they act as a blue print of the intended behaviour of the application. If you don't have this, then it's a complete nightmare if it's a medium - large application as now you have to go and figure out what every use case there is, what it's doing, how it handles exceptions/forks, etc.

Can you give us some background on what you're dealing with?