Game Testing on Mobile Devices


As you might have noticed, the mobile market is on a surge. There is virtually an “app” for everything in your life from budget planning to fitness! There are also thousands of games you can play on your mobile device. As a software tester, this mobile mania is giving you endless opportunities and I would like to share some tips for game testing from my limited experience.
 Know your device
So, you have the super smart phone – the iPhone 4S, the Galaxy S2, the Google Nexus S, the Nokia Lumia… Good! But do you really know what your phone capabilities are?

  • What platform is it running (iOS, Android, Symbian, and Windows Mobile)?
  • Do you know its strengths and limitations (Processor speed, RAM, Storage Memory, Maximum application size, etc.)?
  • Do you know what type of connection can you use (Edge, 3G, CDMA, Wi-Fi, etc.)?

If you do not know any of the above, then I would suggest getting as much information about your device as you can. This is not only applicable to game testing, but also to any type of mobile testing. But the device’s processor speed, RAM etc. are really important in playing your favourite games seamlessly. What’s the point of having that wonderful game if it is subjecting your device to lots of heating due to the increased use of processor power? You are not willing to let your 30K worth smartphone burn for a game, right? J

 UI

With the ascend of tablet computers to the mobile world, more and more developers are creating their games and apps compatible for many devices with a single installation file. For e.g. you could download an app from the Apple app store which is compatible with both your iPhone and iPad. There lies the catch for us testers. There might be screens where the rendering is not properly done in an iPhone screen because the app is showing the page as in an iPad!

As you might have noticed, the games usually have really colourful UI and it is one of the primary things that make a game appealing. So you need to look at the colours used, fonts, icons, button size etc. and finally;

Fail intentionally!

Sounds interesting, right? You have tried so hard and succeeded in beating the computer opponent, and this so called tester is telling you to fail the game levels intentionally?

This could be your most important tip for testing games – learn to fail. Because, when you are failing intentionally, you might be subjecting the game to its most critical test – whether it can behave in the right way when you fail. You are getting competent and matching the computer opponent with all the concentration in this world, it is easy to miss out on what the computer opponent might do in case you fail. I have experienced instances where the computer opponent or your sidekick looked really stupid after I’ve purposefully failed my mission J

Hope my little tips will help you in testing those wonderful games and make your testing much more fun. Have a tip which can be useful for the testing community? Share it!

Thank you for your time in reading my post. Your feedback will be most welcome 🙂

Author Bio :

I’m a Mechanical Engineering graduate, and switched to Software Testing (I would say accidentally, or by necessity :) . But since joining a Software Testing Course in June 2006, I think I’ve made the correct decision. I’m enjoying my role as Software Tester and becoming more and more obsessed with Testing :)
I’m available in Twitter @nandagopalr.

 

Leave a Reply

Your email address will not be published. Required fields are marked *