As the CTO and the person who originally developed the first version of AltTester®, I wanted to share a few thoughts on our journey, where we’ve been, and where we’re heading. This isn’t just a reflection on the past—it’s a look at how we’re adapting to continue delivering value to the game QA and development community.
How It All Started and Where We Are Now
AltTester® was born out of necessity. Working closely with game developers, we saw the challenges they faced in QA without any end to end automation. Initially, our focus was on creating a tool that integrated seamlessly into the Unity Editor, addressing the specific needs of game developers. The first version of AltTester® was simple but effective—a stepping stone towards making game test automation accessible.
We didn’t stop there. To expand testing beyond the Unity Editor, we launched AltTester® Desktop. With AltTester® 2.0, we added WebGL support and recording features, making automation easier for QA teams that didn’t have programming skills.
Altom’s extensive experience in software testing services and consulting enabled us to support AltTester®’s development through a combination of licensing and automation services. From the beginning, we’ve been passionate about open source, believing in its potential to foster collaboration and innovation. For nearly five years, the AltTester®’s development was funded internally using revenue generated by Altom. This approach allowed us to stay independent, remain true to our vision, and cultivate a dedicated community we’re incredibly proud of. However, despite our commitment to open source, we have struggled to turn this approach into a sustainable business model.
A New Chapter: Adapting Our Model
To ensure AltTester® continues to grow and evolve, starting with the next release that is going to come out in the next couple of days, we’re making some important changes:
• Non-GPL SDKs: We are releasing a non-GPL version of the AltTester® Unity SDK that supports UI Toolkit. New features will initially roll out to the non-GPL package, with plans to later include them in the GPL version.
• Unreal SDK: We are also officially releasing support for Unreal Engine with our non-GPL AltTester® Unreal SDK
• Accounts and Licensing: All plans, including the Community version, will now require an AltTester® account and a license key. This change will simplify the license activation process, making it easier for users to manage their licenses while also streamlining the process of switching between the Community and the Pro / Enterprise plans. For us, it helps us better understand and support our user base, enabling us to improve the product for everyone.
• Pricing: We are updating our pricing as well. The Community version will remain free for small studios and companies, but we plan to change our pricing strategy so that studios with revenue higher than a certain threshold will need to use a Pro or Enterprise subscription. We also want to encourage annual subscriptions versus monthly ones, because we know investing in game automation requires a long-term commitment.
By transitioning to a non-GPL model for our SDKs, we aim to make automation more accessible to companies that prefer alternatives to GPL-3 licensing. AltTester® is designed with flexibility in mind, integrating seamlessly with multiple programming languages, testing frameworks, and industry standards—ensuring an easy transition if your needs change. For advanced requirements, we also offer the option to access the SDK source code for an additional fee.
Looking Ahead
AltTester®’s journey reflects both our successes and our learnings. We’re excited about the future and remain dedicated to building a tool that meets the evolving needs of the game QA community. These changes are steps toward ensuring we can continue delivering value while supporting those who’ve been with us from the beginning.
Thank you to everyone who has supported AltTester®—whether you’re a small studio just starting or a seasoned game development company. We’re in this together and look forward to the road ahead.