Q.


How embedded are AI/automated tools in today’s QA environment and how have they made things better, or perhaps worse?


Adriano Rizzo (Payload Studios): Automated testing is becoming more and more a vital part of QA testing in the games industry, and it has to be due to the size of a lot of games these days. Simple tests can now be handled by the automated system and leave QA testers to focus on other trickier areas, especially in open world games where players have a lot more options in terms of gameplay. There might be a fear that this reduces the need for QA, but in reality it can help develop them into better testers and can improve their skills in more rewarding areas. In the long term there’s little doubt it can benefit the quality of the product overall.


Tarek Nijmeh (PTW): AI/automated tools are not nearly as embedded as they should be, in my opinion. However, we are making significant progress compared to a few years ago. Previously, the focus was on adding automation to the backend, but recently, more and more automation tools are used to test front-end mechanics and UI. I think automation, machine learning, and AI are crucial to the success of QA, especially as games become increasingly complex.


Neil Soane (Quantic Lab): AI tools are becoming more and more important within QA, however I believe we are still at a very early stage of understanding how AI will help us with our pipeline. There are some thoughts that AI bots will take over huge chunks of the testing pipeline in the future and to some extent I can see that happening, however I believe that is a little way off and would be instigated and implemented by the developers at a low level. We would always support the clients with new technologies where it is possible for us to be involved, there will always be limitations. Of course, engine tech companies such as Unreal and Unity may well be already going down this road, people much clever than me will know what is possible.


Erik Hittenhausen (Testronic): AI and automated tools are becoming increasingly embedded, but more in development than in QA. However, QA is reaping the benefits of this new technology because the tools mean that we are not working from ‘scratch’ on testing. A decade ago, it wasn’t unusual for a team of testers to start work on a project only to discover that the build wasn’t even working. That just doesn’t happen any more as there are enough tech-based verification steps and checks to ensure that a game is viable. This means that the time of our testers isn’t wasted, but it also means that we have more time to do the things that are better done by humans, such as finding creative ways of breaking the game, etc.


Adam Rush (Keywords Studios): While I’d say there is still quite a bit of manual QA performed, many custom engines and tools exist that do make life a lot easier. Need to know if all areas of a map have been checked? Build an automated heatmap. Need to ensure that a build is stable immediately after it’s cooked? Build an AI that can play the game and run those BVTs/smoke checks, ensuring you can deploy a clean build to the studio. There is still a huge manual component, of course. Many defects created by automation need to be checked by humans to ensure validity and be properly vetted. Automation essentially frees up more time for humans to focus on the quality of a game, reducing mundane and sometimes meaningless tasks so we can really pay attention to making a project shine.


“AI and automated tools are becoming increasingly embedded, but more in development than in QA.”


Erik Hittenhausen, chief service officer at Testronic


February 2023 MCV/DEVELOP | 45


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60