Working as a tester at Testlio has helped me become a better developer.

In addition to testing, I develop games for various platforms including mobile and PC.

The skills required as a tester are useful when creating applications yourself. These skills help me figure out problems quicker on mobile and other platforms.

Developing for mobile

One thing that is commonly used when developing games, as well as programming in general, is a console log. When something goes wrong in a program, it’s useful to have a log showing what happens. It can also be useful when you need to figure out what the result of a piece of code is. Depending on the environment you are developing in, there is not always a console log when testing on mobile phones.

Because of my work at Testlio, I have gained experience using the Android Monitor. This tool from the Android Development Kit records all debug messages from any connected Android phone and displays them clearly.

Recently, I had an issue while working on a mobile game which didn’t make any sense. After booting up Android Monitor and reading the logs it generated, I was able to fix the issue quickly.

Developing for other platforms

Perhaps more surprisingly, testing mobile apps has not only helped me improve as a mobile developer but has also been a great help for other platforms such as PC. When developing any program, whether it is a mobile app, game or computer program, it’s important that the program runs without issues. The best way to ensure this happens is with testing and reporting bugs.

A project I’m working on uses Mantis, an open source, free-to-use bug tracker which keeps track of all the issues in our game. This includes graphical issues, platform-specific problems as well as bugs encountered during playing.

Quickly finding, reporting and fixing issues is an important and constant cycle in game development.
During my time at Testlio, I have written dozens of bug reports and have constantly received feedback on how to improve them. This has resulted in my bug reports becoming consistently clearer. In turn, clear and concise bug reports contribute to fewer bugs and help improve a project overall.

This post by Jimmy Koene is part of a new series written by our community of testers.

Want to join our testing community? Email us: