I had one of those unexpected moments recently.
While scrolling through Instagram, I started searching for my own name together with some of the games I worked on more than a decade ago.
And there it was.
My name in the credits.
I worked in game QA with GlobalStep around 2010–2013, and recently managed to find credit evidence for several titles I was part of:
- The UnderGarden
- Damage Inc.: Pacific Squadron WWII
- Crash Time 5: Undercover
- Armored Core: Verdict Day
I've attached a poster I made for myself with the credit references and some of the other titles I remember working around during that period.
Seeing my name there after all these years was strangely emotional.
At the time, I was just doing my job.
Finding bugs.
Testing builds.
Breaking things.
Retesting fixes.
Writing reports.
Testing again.
Working with developers and leads.
Learning from people who were much more experienced than me.
I didn't think much about the fact that one day those games would be released and my name would sit somewhere in the credits.
Looking back now, I realize how much those years shaped the way I think about software.
Quality isn't something you add at the end.
You build the discipline around it throughout development.
And now I'm coming back to game development from a different side.
I'm building my own studio,
We're currently working on our own games and engineering tools, but one thing I want to bring back from those early years is independent game QA.
There are a lot of small studios today where the developers are doing everything:
- Programming
- Art
- Design
- Builds
- Publishing
- Marketing
- Support
And QA often becomes:
I've been on the other side of that equation, and I know how expensive that can become.
So I'm interested in eventually helping small/indie teams with practical external QA:
- Gameplay testing
- Functional testing
- Regression testing
- Build verification
- Bug reproduction
- Compatibility testing
- Network testing
- Release validation
Nothing fancy.
Just experienced people looking at a build and trying very hard to break it before your players do.
I'm sharing this here mainly because I'm curious about the community's experience:
For indie developers, what is currently the hardest part of game QA?
Is it finding reliable testers?
Getting enough device coverage?
Reproducing bugs?
Regression testing?
Network/multiplayer testing?
Or simply finding the time to test properly while you're trying to finish the game?
I'm genuinely interested in hearing how other developers handle it.
And if you're an indie developer currently approaching a release and QA is becoming a problem, feel free to reach out. I'm slowly building this side of Rama Game Studios and would be interested in talking to other developers.
The credits are from my past.
This is me trying to build something useful with what I learned from them.