Blog

INTRODUCTION

The indie game development scene has witnessed an explosion of creativity and innovation, with countless small teams and individual developers crafting unique gaming experiences. However, the path to success is paved with challenges, and one critical aspect is Quality Assurance. In my case, in the team working on the development of the card game, I am the only QA analyst who deals with testing the entire game. While others are working on specific aspects, my job is to ensure that the entire game runs smoothly. But this experience is not without its challenges.  
In this article, we will delve into my indie game testing journey and explore the various challenges I’ve encountered along the way. 

The challenge of being the only QA in the team 

Testing an entire indie game as a single QA can be very difficult. While other team members oversee specific tasks, my job is to ensure that all these parts work together perfectly. This is a challenge that requires attention, organization and multitasking skills. 
Mostly in the development of indie games, in addition to a small number of full-time members, there are many more part-time members, so there are also part-time members in our team who work on their own and do not always communicate with the QA. This can create additional challenges because the changes they introduce can affect the functionality of the game. As a QA, I am expected to be proactive in monitoring these changes and their impact on the entire game. 

First steps in the world of indie game testing 

It should be noted that this is my first experience in testing of a video game. Before joining the team, I was involved in e2e (end to end) testing using Cypress, a popular web platform test automation tool. I considered applying my previous experience with Cypress using the same approach here to speed up the regression process. 

However, I encountered one significant challenge. The game is rendered within a single canvas, which means that it is not possible to easily access and manipulate certain elements within the game as you can with traditional web pages. This was the first sign that e2e testing was going to be challenging. Without the ability to access individual elements within the game, it was not easy to write accurate tests to verify the functionality. 

Alternative approach: Unit tests  

Given these challenges, the team opted for a different approach. The game is covered by unit tests that are regularly maintained and updated. These unit tests have proven to be extremely useful in uncovering issues and bugs within the game. Although I could not directly automate e2e tests as I did with Cypress, unit tests proved to be a great alternative for a deeper understanding of the game’s functionality and monitoring its behaviour during development. 

Testing the entire game and regression 

In addition to testing new functionalities, my job also includes regular regression testing. This is especially challenging in the world of indie games where quick fixes and upgrades are often made. Every time a new patch is planned, I must quickly and carefully check all the functionalities of the game to make sure there are no unexpected problems. 
Writing detailed tests with clear steps can be a time-consuming process and too much work for the only QA in the team. In my case, transferring the existing checklist to QASE – Test management software was a solution that enabled more efficient monitoring and test management. This meant that I didn’t have to rewrite all the tests I inherited, but simply transferred the existing tests into this excellent test management software and sorted them into categories.

CONCLUSION

My first step into the world of indie game QA testing was filled with challenges, but all these challenges are met with a sense of satisfaction and contribution to the team. When you see the game working flawlessly and the players enjoying it, all those challenges become worthwhile. 
Indie development can be turbulent, but I’ve learned that it’s important to adapt to the specifics of each project. 

In conclusion, my experience as the only QA tester in the team was challenging but also rewarding. I learned the value of teamwork, adaptability and different testing tools. Although I could not use the same tools and methods as in the previous experience, in addition to manual testing, unit tests became a key part of our process and helped us to maintain the quality of the game at a high level. I will always remember this experience as my first step into the world of game testing.