You're in charge of testing for a new game. How can you be sure it's the best it can be?

Un jeux est comme une relation privilégiée avec l'utilisateur. aussi abouti puisse t il être un jeux se doit de réserver de la place pour sa propre mutation. après tout le gaming est un art en constante évolution. les jeux qui en sont le cadre doivent donc forcement faire de meme. c'est d'ailleur ce qui explique la pratique dorénavant commune de la mise à jour et la production de contenus adaptés à l'actualité, la saison, ou encore le caprice des développeurs.

While defining the goals, plan to create a checklist. This checklist should have pre-requisite items (No of 100% complete modules coming for the test, number of prototype modules coming for the test etc) build wise that is going to help in order to accept the build for testing based on the scope defined from the 1st build that lands in QA. This seems irrelevant but this becomes helpful when all the features are not coming into a single build but in multiple builds.

Have a checklist for each category of your defined goals eg from a UX perspective, Accessibility, Balancing, Bugs, and Mechanics. Ask yourself what are you testing, and what are you hoping to achieve from the playtest based on some of the categories I mentioned above. Document the goals along with the actual results from there you can define if there is anything that's a player block and needs to be fixed immediately.

We always work with a clear checklist. This checklist has to be adopted for the target group. Age, Gender etc. Testing and these checklists are the most important tools in our arsenal.

A test plan or procedure is the best way to ensure the results you get by the end of the process. Make sure all points to be analyzed are included in the procedures.

While planning the test, time slot/schedule for the play test should also be planned and it should be led by the QA team. The play test usually happens when the QA team has enough confidence on the game. The whole idea is to call multiple people from the various departments to come in a room and do a experience test from their end and report bugs, suggestions or whatever they don’t feel right.

Testing should be planned as close to development schedules as possible. If you can, be in the room with the folks making the game so you get the clearest idea of what they're doing. Whether they let you in that room or not, get access to their documentation, and start there before its done. Look for holes in the plans. Ask questions. Build a test off of those standards and off what else you think might go wrong. You can't get everything, so look to ensure the ideal player path is clear of all obstacles. Then, branch out to other common paths and look for major problems. And ensure time for ad hoc is included in that -- nothing finds a crash quite like letting the QA testers free to "see what happens if..."

When executing test cases, if you have a team that the work will be split between, assign things based on what your team members do best. Sure, any one of them could run any test, but if you know one does analytical things better-- assign the most nitty-gritty-detailed test to them. If you know one has a better gameplay sense and can pull of harder inputs-- assign the more complex system function and performance tests to them. Not only will the work get done: it will be done with passion and care. They're good at what they do because it matters to them. This is especially true of testers more experienced with the genre of game: they know what real, game-breaking player behavior looks like, and find it before players ever get the chance.

During execution, QA team should also have some bandwidth to help development teams to reproduce/debug the issues. There maybe a case where a bug is reported but the developers are not able to reproduce them.

Incorporate automated testing tools to execute repetitive tests quickly and efficiently. These tools can cover regression testing, functional testing, and performance testing, saving time and reducing human error.

The most important part in our checklist? A simple checkbox: Play again? Yes | No If there is a no everything else has to be repeated. Back to the drawing board.