QA Game Testers play an integral part in developing Goblin Stone. It is a vital process that ensures that everything runs smoothly and the quality of the game. In this Devblog, we will share with you the insights from our QA Lead, Keith, on how he perceives game testing for Goblin Stone.
Firstly, game testing is not all fun and games. It involves long hours of sifting through game glitches, bugs, and other technical issues. A good eye for detail, the ability to multitask, and effective time management are all essential attributes of a QA Game Tester. Let's jump in with Keith as he share his thoughts on how he communicates effectively and works closely with game developers, designers, and other team members to identify and resolve issues.
What’s it like being a QA Game Tester at Orc Chop Games?
I can say, being a QA Game Tester here at Orc Chop Games can be both exciting and challenging.
Exciting in a sense that I will be playing an awesome game and be part of this awesome team who is currently making not only a great game, but a game to which I think will be loved by many.
At the same time, it’s challenging as the primary task of a QA Tester is to play the game extensively. This might sound like a dream for many gamers, but it often involves playing the same game repeatedly to find bugs, glitches, or any other issues.
As a QA Game Tester, I need to be attentive and have a strong eye for detail to spot even the slightest of errors and inconsistencies in the game. I need to meticulously test different aspects, including gameplay mechanics, graphics, audio, controls, and user interface.
Effective bug reporting is crucial for the Development Team to identify and fix the issues. It requires accurate report of any issues I've encountered in the game which involves documenting the steps to reproduce the bug, providing screenshots or videos, and describing the impact it has on the game experience.
As I need to work closely with the game developers, designers and other members, communication and collaboration is also one of the key factors for a successful production. Effective communication skills are important to relay findings, collaborate on solutions, and ensure the game meets the desired quality standards.
As technology advances and new games are developed, I must be able to adapt, learn quickly and stay updated on the latest industry trends, game mechanics, and testing techniques to provide relevant feedback during the development process. With that in mind, I usually employ various testing methodologies such as functional testing, regression testing, feature testing, and other testing to ensure the game performs well across different scenarios.
Meeting project deadlines is also challenging. I need to prioritize tasks, complete the test cycles within a given timeframe and adapt to changes in project schedules.
Lastly, the one factor that really challenges me is that I need to identify complex bugs, reproduce hard-to-trigger issues, or suggest improvements for game mechanics. Strong problem-solving skills are essential to overcome these obstacles.
Can you walk us through your thought process when it comes to game testing, like giving us an example of different types of testing you handle in Goblin Stone development?
First and foremost, I make sure to thoroughly read and understand the game requirements, specifications, and objectives provided by the Dev Team. A test plan is created based on Goblin Stone's features and mechanics. Following the test plan, test cases would be created to be used for testing. Bug identification and reporting comes next as I need to document the issues I've encountered and provide detailed and clear description of the issue. Screenshots and video evidence are taken and attached to the bug report in order for our developers to quickly assess and reproduce the issue for bug fixing. Once issues are fixed, I conduct regression to ensure the previously identified bugs have been resolved successfully.
As for the different types of testing, I usually do the following types of testing while working for Goblin Stone:
Functional Testing - This is to ensure all functions of the game are working without issues
Smoke Testing - After a build creation, I usually conduct this type of testing to ensure to all basic and critical functions in general are present and working throughout the whole FTUE session
Regression Testing - Regressing issues that is deemed to be fixed by our developers
Sanity Testing - To determine that the bugs are fixed and that no further issues are introduced to these changes
Exploratory Testing - Testing which does not require test cases to follow and just explore and find any issues while playing the game freely.
Testing the Homebase functionality
Combat test using Unity
What do you think is the most difficult part of testing Goblin Stone?
Personally, the User Experience and playtesting is the most difficult part of testing Goblin Stone.
Evaluating the game from a player's perspective to ensure it is enjoyable, balanced, and engaging can be a difficult task. Conducting extensive playtesting, collecting feedback, and iterating on the game design with the help of our designer can help improve its overall user experience.
What are some common issues that you look for when testing, and can you share with us the funniest experience you encountered while doing the testing?
For starters, Visual issues are the most common issue I look out for during testing. Who wouldn't want a clean game to play?
I remembered one time, encountering an issue with the Credits. The Goblins displayed on the Credit page are either blind, no nose, missing ears and other various missing body parts. I can't stop laughing at how they looked!
Funny Goblin model bug
How do you communicate with developers to collaborate on finding a solution to fix an issue encountered in the game?
When finding a solution to fix an issue encountered in the game, I usually assign the bug tickets to our developers. This will also notify them via the reporting tool that an issue was assigned to them for bug fixing.
Aside from that, since our developers are working overseas, we usually communicate and collaborate via Discord. Discord is our primary means of communication within the whole team and in urgent cases that need to be relayed immediately we use any accesible means of communication.
How do you balance the need for thorough testing with time constraints and deadlines?
Balancing thorough testing with time constraints and deadlines is challenging. However, I usually do these strategies in order for me to manage the balance effectively:
1. Prioritize the feature, functionalities, or areas of the game that are critical to its success and prioritize testing efforts accordingly. Identify high-risk areas where issues are most likely to occur and allocate more time and resources for testing those aspects
2. Create a detailed test plan that outlines the scope, objectives and timelines for testing. Break down the testing process into smaller tasks and allocate time for each task. This allows me to have a clear roadmap, ensuring all critical areas are covered within the given time constraints.
3. Conduct a risk assessment to identify potential risks and their impact on the game. Focus on testing areas that have a high potential for critical issues, while reducing the level of testing for less risky or less impactful issues.
4. Implement iterative testing cycles where testing is performed in multiple iterations throughout the development process. This allows for early detection and resolution of issues, reducing the chances of last-minute delays.
5. Maintain open and transparent communication with the developers, design team and producer. Clearly communicate the progress, challenges and potential risks associated with testing to manage expectations and adjust schedules if necessary.
6. Implement agile methodology like the daily scrum or we call it here as 'Stand Up'. This allows for regular feedback and flexibility to adapt the testing approach based on project needs.
7. Identify test cases that provide the maximum test coverage with minimal time investment. Prioritize test cases that have potential to expose multiple issues or cover multiple aspects of the game.
8. Regularly review the testing process to identify areas of improvement.
9. Set realistic expectations and communicate early with the producer about the limitation of testing within the given time constraints. It is important to strike a balance between thorough testing and meeting deadlines.
While time constraints and deadlines are important, quality should not be compromised. It is crucial to find a balance that ensures adequate testing while delivering the game within the agreed-upon timeline.
Keith reviewing bug reports with the Producer and Community Manager.
Before we end this devblog, what advice or recommendations would you give to someone who is interested in becoming a QA Tester for a video game?
If you really want to become a QA Tester for a video game, you need to have a genuine love and understanding about video games. This will fuel your motivation and enable you to approach game testing with enthusiasm and dedication. Familiarize yourself with various gaming platforms, operating systems, hardware configurations and game development tools. Understanding the technical aspects of games will help you in identifying and troubleshooting issues effectively. Also, familiarize yourself with software testing concepts, methodologies, and best practices. Consider learning about testing techniques, bug tracking systems, test case creation, and regression testing. There are many online resources, tutorials, and courses available to help you learn these skills.
As a game tester, you need to have a keen eye for detail to identify and document bugs. Practice observing and documenting issues with precision. You may also look for opportunities to gain experience in game testing. This can include participating in beta testing programs, modding communities or by contributing to open-source game projects. Even entry-level positions in the industry can be a good starting point.
Improving communication as effective communication is crucial in the testing process. Develop your ability to provide clear and detailed reports of the issues you encounter while testing. Good communication skills also help when working with the developers and other team members.
If possible, you may attend QA Tester events or join online communities. Engage yourself with professionals in the gaming industries. These can provide valuable insights, job opportunities and mentorship.
Be adaptable and flexible. Game Testing can involve repetitive tasks, tight schedules, and working under pressure. Being adaptable, flexible and having a problem-solving mindset will help you thrive in this field.
The gaming industry is ever-evolving. Stay up to date with industry trends, new technologies and emerging testing techniques. This will make you a valuable asset in the field.
Remember, QA testing for video games requires diligence, patience, and an eye for detail. With dedication, continuous learning, and a passion for gaming, you can work towards becoming a successful QA tester in the gaming industry.
