How can you balance objective feedback with the subjective nature of game testing?

Do not work in a silo. Make sure to use your alpha and beta to capture detailed user feedback. Too often, game studios release their alpha/beta then simply look at game metrics and/or a generic, multiple choice questionnaire to gauge user feedback. Go beyond that. Host focus groups. Prepare specific questions. Offer alternatives for A/B testing. The more data you capture, the better of a fact base upon which you can make decisions.

In my experience, the Testing team should first understand the game and the vision of the game we are testing. Every tester in the team must have clear understanding of their deliverables based on the production team requests. The testing teams must think about the experience that we want our real players to have and be as diverse as possible in testing to ensure the players will have the memorable experiences when they play it. Should be Co-DEV and equally contribute to the development, by providing feedback on the quality of the game with constant new implementations and how we can improve on certain areas to provide better gaming experience. Testing the game as per the end-user's perspective and be creative with the testcases.

Balancing objective feedback with the subjective nature of game testing involves establishing clear evaluation criteria, incorporating diverse perspectives, and recognizing the inherent subjectivity in player experiences. Utilizing a mix of quantitative data and qualitative insights allows for a comprehensive assessment that considers both measurable elements and the nuanced aspects of player preferences and engagement.

Effective game testing begins with a deep grasp of the test's goals. Dive into the key features and mechanics earmarked by developers for scrutiny. Uncover the essence of sought-after feedback—whether it's usability insights, feature impact, or overall player experience. Equally crucial is discerning the preferred reporting format—is a structured report the need, or does an open dialogue better suit their objectives? Tailoring your approach based on these insights transforms your feedback into a targeted tool, ensuring it resonates with the specific needs and goals of the test. Let's navigate testing terrain with precision, offering insights aligned with game testing objectives!

Der Test eines Spiels sollte sich vor allem an den eigenen Erfahrungen orientieren. Tests sind immer subjektiv und Leser:innen k?nnen mit den eigenen Ansichten und Erfahrungen viel mehr anfangen, als mit dem Versuch, Mechaniken und Grafiken objektiv mit anderen Spielen zu vergleichen.

From a psychological perspective you can use theories like the well-established self determination theory (SDT) to understand and structure your experiences and your feedback. SDT postulates three basic psychological needs: competence, autonomy and relatedness. The great thing about SDT is that it has been researched with games and it was shown that games that sell better were better in fulfilling those needs. When giving or receiving feedback you may want to dig deeper to understand which of those needs might have been frustrated – from there you can work on solutions.

Very important to give specific feedback. I always use FBI tool while giving feedback. FBI - stands for “feedback based on impact”. What impact / impression it left on me after testing. Possibly detail Pros and cons. Always be constructive in your approach.

In-game testing, precision is key. Could you offer specific, factual feedback? Rather than labelling the game as "boring," pinpoint issues like level design, emphasizing the need for variety and challenge. Move beyond generic statements about graphics, highlighting nuanced issues like blurry textures and inconsistent lighting. Elevate your feedback with examples, screenshots, or video clips, turning opinions into tangible insights. This approach enhances clarity, providing actionable data for developers. Navigate game testing intricacies with a keen eye for detail, ensuring your feedback guides improvement!

One thing I've found helpful is when you test the game and give feedback. You can't do this same to all testing steps. For example, when you need to test a game storyline or translation you will need to be more detailed, while you test mechanics and game design you will need to be more creative and open. Screenshots and video clips are kings of proof here, try to screenshot and point out the issue as specific as possible, you also can provide before/after steps/scenes to help the developer verify the issue. If you know the game is boring, then you know what the game lacks, try to express this as a strength and weakness point you found, it will become more insightful as feedback.

While providing the feedback to the development team, one should be very specific with the actual scenarios in the game and how they may impact the experience of the users. Can provide details to explain the feedback more clearly like screenshots and videos, be it a real life, movies or any other games that explains the impact of having the new suggestions in game. Feedback should never deviate from the actual game idea or the storyline or the game mechanics, as testing team should always be in-line with the vision of the game, should consider the limitations of the architecture and engine the game is being developed upon.

Understanding the vision of developer is very important, before testing. It helps in visualising the purpose of the development, and what it is addressing and trying to deliver. Remember we all carry personal preferences / Biases, we must not get carried away with that while giving feedback.

Recognizing the subjective nature of game testing is vital. Each player brings unique tastes and preferences. Acknowledge your biases and distinguish them from objective flaws. Disliking a genre doesn't deem a game objectively bad. Express personal opinions but respect developers' creative choices. Striking this balance ensures your feedback is constructive, embracing diversity in player perspectives. Let's enrich the testing dialogue with a mindful acknowledgement of subjectivity, fostering a collaborative journey toward game improvement!

The more diverse group is better, you can't expect you will get the same answer from any user test. Keep trying to elaborate your testing or survey results with market conditions and research. As a gamer, is OK if you have a certain preference for genre, design, or play style. You can express your personal opinion, and you can compare, but as a game tester, you need to keep giving constructive feedback and feedback based on goals. Point out your perspective, give an answer based on your test experience, and report this as you found. Just share your opinion.

When I test video games for my clients, I try to make give feedback in two categories: the subjective 'did I enjoy the game and do I believe it was fun' and the more objective 'how does the game perform, what is the quality standard and is it intuitive enough (or did I receive sufficient explanation in the tutorial)'. Too often, feedback is like: "I like / don't like this game". While it ultimately boils down whether players like it or not, there are parts of the game that you can feedback more objectively upon.

Beim journalistischen Testen eines Spiels sollte das im Vordergrund stehen: Obwohl der Test an sich nur subjektiv sein kann, ist es m?glich, eine weitestgehend objektive Sicht für Leser:innen aufzuzeigen. Greifbar macht das eine pers?nliche Betrachtung oder das Schildern der eigenen Erfahrungen: Was hat mir aus welchem Grund Spa? gemacht? Welche andere Spiele haben dasselbe in mir ausgel?st oder auch nicht? Etc. ...

Game testing is not just about testing the game itself; you can use it to build a community or ambassadors. Testing can be a privilege and you can communicate its importance and reward the testers from the community. Testing itself can be gamified without losing data relevance. The volunteer testers should be motivated to play as much as possible, be successful in the game, and give you a picture of all the stages of the player's cycle. Try to achieve a friendly atmosphere where your testers are open to sharing the feedback, discussing it, and feeling that they contribute to the good thing - which means opening the communication channels with them or doing the direct testing.

Game testing extends beyond bug hunting—it's an opportunity to applaud successes. Beyond glitch reporting, acknowledge captivating storylines, memorable characters, enchanting music, captivating art, or innovative gameplay elements. Positive feedback uplifts developers, fostering morale and showcasing appreciation. This two-way dialogue aids game improvement and nurtures collaboration. Let's not just find flaws, let's celebrate the gems that make gaming truly remarkable!

Wichtig ist vor allem, das Spiel als Ganzes zu sehen: Wie gro? ist das Team dahinter? Was war dessen Vision beim Art-Style, beim Game-Design, bei der musikalischen Untermalung? "Life is Strange" war von der Grafik her zum Beispiel nicht mit AAA-Titeln zu vergleichen, überzeugte aber als Gesamtprodukt Massen. Darauf kommt es an!

There are different aspects to the games. And every one of us sees that differently. For example, today's games are HUGE in GB and take plenty of space, and that can take effect on the games. For me, the gameplay itself plays a great role and the graphics are not always important. The movement of the characters, the interaction with the environment, the story itself, the level design, and the game ENGINE in general. I've played hundreds of games. I started gaming when I was 5 years old, from Super Nintendo to high-end PC and now PS5. There are MANY aspects when judging a game, and sometimes a different IDEA can be good or bad. Example: Splinter Cell Blacklist. Third-person game, lot of combat animations, one level first person, bad choice.

In the realm of feedback, the essence lies in being both respectful and constructive. Steer clear of harsh or rude language that may dishearten developers. Recognize their passion and hard work in crafting a game. Instead of mere criticism, present suggestions, solutions, or alternatives to address encountered issues. Infuse your feedback with politeness, honesty, and support. Express gratitude for the opportunity to test their game, fostering a collaborative spirit where constructive critique paves the way for improvement. Let's navigate the feedback landscape with a blend of courtesy and insightful suggestions!

Balance objective feedback by using quantifiable metrics for functionality and performance. Includes diverse playtesting sessions, Prioritise critical issues and iterate on testing for continuous improvement. Categorise player feedback and involve expert reviewer for informed perspectives. Provide context for subjective feedback to developers.

Direct feedback in a way that avoids demoralizing language is necessary however expressing the concerns where it derives from can be critical. Providing key concerns, actionable steps to correct, as well as having an open mind towards developmental feedback are necessary to extend a better level of communication with developers to achieve the best outcomes for the game. There are multiple ways to communicate feedback and by keeping an open forum you will be able to a strong balance between what is possible from a developer angle and what is necessary from a gameplay/marketability angle.

Some strategies that I could think of implementing would be: a)To define the clear testing objectives b)Using Surveys c)Defining the evaluation criteria d)Gathering qualitative feedback from the testers e)Using diverse group of testers as different players may have different subjective preferences, and a diverse group can help capture a wide range of opinions. f)Focus on Player Experience - Though this is subjective but it can still be evaluated through retention metrics, playtime etc. g)Maintain regular communication with the team. I believe by clearly defining objectives, proper evaluation methods, and keeping the lines of communication open, you can effectively incorporate both types of feedback.

It's always a good idea to separate and define quantitative and qualitative metrics. This, in addition to clearly defined goals and well-studied evaluation criteria, can be used in numerous ways: surveys, playtesting with diverse groups of people, internal testing, etc.