Originally by: Siege

---

Testing would be, for instance, going from system to system and each one you get there you warp around and constantly scroll the new seamless map in and out, repeatedly, looking for inconsistancies of any type. For instance, does the map show you in the right system? Does it freeze/lag? Does it have any spots where the graphics get all funky? Can you stay in the map, jump to a new system, and have it update? or does it crash? What happens if you open a cyno, unzoom the map, and jump a few systems away in a capital ship? What if you are cloaked with the map open, and change systems, while trying to reload weapons, target the gate, launch drones, and somebody lights off a doomsday weapon, all at the same time?

For ship combat, it's repeatedly shooting your friends with different ammo to test out the resistances to make sure they match in the new ships. Also, plot out the damage done and see if it coincides with the stated bonus. Does the fitting shown in the item info screen match what you can do? I.E. does it say 4 turrets but you can fit 6? Can you repeatedly hit with artillery if your buddy is in a MWD interceptor circling you at 3000m?

Basically, you want to look closely at every little bit of detail in there to make sure it works as advertised with no ill effects or un-intended advantages. You're looking for problems in the code, which means you have to repeat the same things many, many times and trying to get as detail oriented as you can. Is everything spelled correctly? Does anything cause you to crash, if so, keep repeating it until you KNOW what causes it. Don't just randomly send in a bug report the first time something odd happens, make it happen again, and again, and again first. Try to figure out WHAT causes it as close as you can, THEN send in the bug report.

Think of it this way. Imagine putting in 'Super Mario Brothers' and having to play level 1-1 for 8 hours straight, and writing down everything that seems unusual or out of place. Then, you get a new version, and have to do it all again.

Welcome to good testing 101.

---