How We Do It – Game Automation Testing

How We Do It – Game Automation Testing
People are surprised when they see the testing report we give them a day after they sent it to us. They wonder how we were able to test a game so fast and return such detailed results.
It’s something that we pride ourselves on. With the years of mobile device experience in our company’s leadership and workers who have testing experience and enjoy game testing, we continue to build a testing experience that can beat the competition. Today we decided to give you a quick look at what our company does and how effective it is at quickly testing and reporting in as little as 24 hours.

Registering your game

The first step is to register your game into the queue so we can create a task for it. Registration is easy. Just follow this link and fill in your Name, Company, Contact information, country, and a password.
Unnamed QQ Screenshot20151124145039           Unnamed QQ Screenshot20151124145023
After that you can enter your account and create a new task. There are a few questions asked about game engine, platform, and other useful information for the testers.

Preparing your game

Next we have one of our testers prepare your game by making a script that loads your game to the phones, starts the app and then go through the game. This includes login, tutorial and other gameplay. The tester then closes the game and ends the script. The script is then used for instructions on each of our phones. Each phone will make the same movements and tap on the same spots on each phone checked.
TestBird Company Video.mp4_snapshot_01.25_[2015.09.09_10.52.05]

Export to the phones

Every phone used for the test will be uploaded with the app and script. When they are ready, they start to take screenshots of the screen and create a log of what happens during the test. The phone then starts the script and will recreate the actions of the first test until the script ends. All data during this point can be viewed in the report for your convenience including memory used, CPU temperature, CPU % and more.

Creating the report

The report will now start to be built from the results including any crashing, failures, and other large issues being looked at by testers to confirm and locate the point of failure. The report is then compiled and sent to you including additional information on optimization. For a sample copy, please visit this link.

Comments are closed.