When going through your internal QA process, It’s very important that you segregate each type of bug in order to simplify recreating it as well as identifying where in the code it exists for the developers. At a certain point, they’ll be able to figure out where exactly most errors lie once they see such data represented as this;
Total Bugs by Category Chart .pdf
From there, they’ll be able to do a two pronged attack in regards to adding polish to the MMOG. Such bugs must be monitored from both the server side as well as the client side. We at the Tukko labs make sure we can view both types of data in order to run through the simulations better as well as keep a more informed development team with the data we’re able to monitor, translate, and report.
