My primary specialization at the moment is as a QA Engineer.
I've been passionate about video games since childhood, with some of my favorites being Warcraft, ECO, Divinity, and the Assassin’s Creed series. My love for gaming began when my brother and I got a first console, where I played Goal 3, Battle City, and Battletoads. As I grew older, I started visiting PC gaming clubs and became fascinated with Warcraft III and Counter-Strike, though Warcraft III made the biggest impression, especially with its custom maps and multiplayer. Later, I delved into MMORPGs, starting with Ragnarok and eventually becoming deeply involved in World of Warcraft.
In 2018, I shifted my career into game development. Initially, I began learning programming, but soon realized that testing and game design were my true interests. This led to my role at Strange Loop Games, where I worked on the development of ECO for 5.5 years. I spent the first three years as a QA Engineer, responsible for testing new game features, conducting regression tests, and identifying bugs. I later transitioned to the role of QA Lead, managing a team of four QA engineers.
I'm looking forward to continue my career in game development, working on exciting projects that challenge what games can be. I enjoy collaborating with talented people who care about creating fun and engaging gameplay, where I can share my ideas and skills to help make great experiences for players.
Unfortunately, since we moved to another bug reporting system, I can't link newly created bug reports. However, I'd like to add links to some of my old bug reports and suggestions that I created when I worked as a QA Engineer. You can also see all my bug reports created on GitHub.
- Chunk loading problem, Crash with "objects in the world" tooltip - Bugs were created with conditions that allow for easy reproduction by the developer.
- Camera glitches if you press ESC in the beginning of Meteor Tutorial, Hint overlaps when hold selecting form type more then 1 sec - Adding screenshots, GIF or videos to the issues.
- NullReferenceException with reconnect to server, Caught exception on Player while in NetObject ReceiveInitialState. BSON, A few NRE during disconect from server on avatar - Constant monitoring of errors in the log to ensure that the log file remains clean and is not spammed with errors that hinder tracking other errors in the log file.
- Can break hammer controller, Stuck in Tab mode after editing a list and cancel selection, Receive Permission contract crash - Adding errors from log files so that the developer does not waste time investigating logs.
- Eco server take a lot of CPU- Monitor performance degradation. Also for that goal I created a special world to compare the different game versions with the same condition.
- Minimap navigation QOL, Improvement for Displaying markers on the minimap , Extending the functionality of creating currencies - Constant feedback to improve UI/UX, add some quality-of-life enhancements for users, and suggest feature improvements.
I can't show you many of my test cases and checklists because they are in private repositories. However, I can provide
When I joined the team, there wasn't a proper test plan. We only had a small checklist of about 60-80 rows in a Google Sheet. It was a small checklist for such a large game. My colleague, who started working with me at the same time, and I divided the game into different parts and began improving our test plan by adding more cases, including negative test cases, since the original checklist mostly covered only positive ones. After some time, our test plan became so large that working with the Google Sheet caused it to freeze. The document I provided above is my first attempt to split that large Google Sheet into six documents based on the game's features. This document is for testing the Economic part (which is actually a small portion of the final economy document). As you can see, we have a detailed test plan for Contracts, Work Parties, and Store, while Economy Viewer, Exchange, and Mint are not as detailed yet since they haven't been redone. Also, because this is a copy, the links to the game versions are broken. In the official document, everything was properly set up.
When I was appointed as QA Lead at the company, things were going quite well. The team was expanding, and including myself, there were 6 QA members. However, one of them worked separately with their own team, focusing on the game’s website and wasn’t directly reporting to me. Two of the testers were newcomers, and I realized that our checklists in Google Sheets were not detailed enough for them. Some of the more detailed ones were good, but still not detailed enough for training purposes. After discussing this with our Producer, CTO and CEO, I received approval to implement a Test Case Management Tool. I conducted research to find the most suitable one for us. I looked into all the popular tools: TestRail, Qase, and TestIt. But the final decision came down to TestLodge and Sleekplan, as our budget was limited. Ultimately, we chose TestLodge because it could be integrated with ClickUp.
It was quite an interesting time, where I gained a lot of experience, including learning from my mistakes. At the same time, the migration from Google Sheets to TestLodge was made easier by my prior educational background as a Metalworking Process Engineer, which helped me create detailed test cases.
