Our Story in Game Testing

Building reliable gaming experiences through meticulous testing and genuine partnership with developers since 2019

How We Started

Back in 2019, I was freelancing as a game tester when I kept running into the same problem. Developers would get their games back with generic bug reports that barely scratched the surface. "Button doesn't work" or "game crashes sometimes" — that kind of unhelpful feedback that left everyone frustrated.

So we decided to do things differently. Instead of rushing through test cases, we started treating each game like it was our own project. We'd spend extra time understanding what the developers were trying to achieve, then test with that vision in mind.

What began as a two-person operation in a shared office space has grown into a team of dedicated testers who genuinely care about making games better. We're still based in Taipei, still obsessing over the details that matter, and still learning something new with every project we touch.

Game testing workspace showing multiple monitors and testing equipment

The People Behind the Process

Kjetil Lindberg, Lead QA Engineer

Kjetil Lindberg

Lead QA Engineer

Eight years of breaking games professionally. Specializes in finding the edge cases that slip through automated testing. Has an uncanny ability to crash games in ways developers never expected.

Team collaboration during game testing session

Testing Team

Collaborative Approach

We work in pairs on complex projects because two perspectives catch more issues than one. Regular team discussions help us spot patterns and share techniques that improve our overall testing quality.

Eira Blackwood, Senior Test Analyst

Eira Blackwood

Senior Test Analyst

Former game developer turned tester. This background helps her understand both sides of the development process and communicate technical issues in ways that actually help developers fix problems quickly.

Detailed bug documentation and analysis process Quality assurance testing environment with multiple gaming platforms

What Drives Our Testing

Real Player Perspective

We don't just follow test scripts. Every game gets played the way actual players will experience it — including the weird stuff players do that wasn't in the original design. This approach consistently uncovers issues that formal testing procedures miss.

Detailed Documentation

Our bug reports include reproduction steps, system specs, screenshots, and context about when and why the issue matters. Developers tell us this saves them hours of investigation time compared to vague reports from other testing services.

Honest Communication

Sometimes we find issues that aren't technically bugs but could frustrate players. We flag these usability concerns alongside critical bugs because preventing player frustration is just as important as preventing crashes.