Ok before i get flamed sum credentials for claiming to know what i know:
1) I try to sign up and test any game that has a public beta/alpha test, a notable one, sfc2 i help in (tho i never did make it past the dyna login screen =\
2)I actually got payed to QA with Sony Interactive in PSX games and PC ported games.
Ok now that that is there he is basically how Sony did the QA, i believe it's pretty much standard crap in the industry.
Step one) The game (or patch) is received, a lead tester (interface between the QA testers and programmers that make fixes) is given the game, he/she goes over it for a day or two getting all the obvious bugs written down and catalogued.
Step Two) A QA team is formed to test the game, in sony we got to play ones we wanted, or in the case of big blockbuster surefire games people were assigned.
Step Three) tester start to bang away at it, the go over in phases different parts of the game, like one period they are all testing single player, another multiplayer etc etc When they run across a bug normally they try to get it to duplicate easily and then write a step by step report on how to do it. This is very difficult sometimes because you might be sitting there and it just happens, and if its a major bug (crasher, or corrupter) you have to figure out how you did it. Some times this takes 4ever!
Step four) At sony we did it in weekly chunks or after a certain amount of bugs were reached (based on the bugs severity). Like they r not going to reprogram a game if they have two bugs that can only be reached if you turn off the sound start a single player game all the while punching a certain button, in a certain order. ( you may think i'm lying but sometimes that's what you test, no sound holding down y button all sorts of crazy things) After all that the lead tester sends the bug database over to programmers so they can come up with another REV (or revision) to start the program over.
All of this is done over and over till they reach a point where is has an acceptable (many games this is extremely flexible term *cough* gameday '98 *cough*) level, and has done a certain amount of "tester hours" now if your talking like 100 tester hours, this is the amount of time it has been tester so if tester A tests the game 8 hours and tester B does it for another 8 the game has completed 16 hours, this is reset every rev that is received.
OK i hope this helps out a little bit for everyone here that doesn't understand how the QA process works, and believe me with a thing like this the longer it stays in the QA department the better it is! Just to let you know some things i tested stayed in the department less then 12 hours! (the whole department was pounding it) the longer you take the more likely you are to find problems.
-Pharacon
PS: See all you guys on the triangle ROMULANS KICK BUTT NOW WAIT TILL I GET SUM WORKING WEAPONS I'll be unstoppable!