VIDEO

GAME
TESTING
GUIDE

The ultimate way

to elevate your
product to new
heights

www.qatestlab.com
CONTENTS
Video Game Testing 101

3 LVL 1. Who are Game Testers?

4 LVL 2. Testing in the Game

Development Life Cycle

6 LVL 3. Test Documentation

7 LVL 4. Types of Game Testing

Techniques

10 LVL 5. Bug Reporting

11 BOSS FIGHT. Most Common Video

Game Bugs

Copyright 2020 © QATestLab. All Rights Reserved 1

Click the section
to jump ahead INTRODUCTION

Video game creators have the However, game testing is a

INTRO
DUCTION ongoing task of ensuring complicated process. It is often
maximum quality while very technical in nature, with
developing magical worlds and processes and outputs riddled
LVL 1 breathtaking challenges. Market with terminology. It is also quite
Who are competition is ever-increasing, difficult for a non-tester to
Game Testers? and conformance of the game to determine the depth of test
high customer expectations coverage, frequency, critical
needs to be continually areas, required testing types,
LVL 2
assessed. and manage risks associated
Testing in the with potential system failure.
Game This is where Game Quality
Development Assurance comes in — the That is why many game
Life Cycle ultimate way to elevate your development teams choose to
product to new heights. appoint a trusted QA and
Undertaking a series of software testing provider to help
LVL 3 well-planned and accurately them conduct the necessary
Test reported tests provides insight defect management procedures.
Documentation into product weaknesses and If you would like to leverage our
provides the support required to bug detection superpower,
remove the defects. check out this guide with
LVL 4
practical advice on carrying out
Types of an effective, value-for-money
Game Testing game testing program.
Techniques

LVL 5
Ready? Let’s get started!
Bug reporting

BOSS FIGHT
Most Common
Video Game
Bugs

Copyright 2020 © QATestLab. All Rights Reserved 2

Click the section
to jump ahead WHO ARE
GAME TESTERS?
INTRO
DUCTION
Game testers find bugs as
early as possible and make
LVL 1 sure they get fixed.
Who are Game testing can be brought
Game Testers? into play throughout the
development lifecycle. In
general, a game is ready to enter
LVL 2
the testing phase once its
Testing in the prototype is available.
Game
Development The golden rule states that the
Life Cycle tester and the developer should
not be the same person, as the
objectivity during defect analysis
LVL 3
is crucial for game quality. It is
Test also useful to note that the
Documentation duration of testing is equivalent more than just playing the
to 40% of the development time. game. Being a good tester
Therefore, concentrate on the requires competency,
LVL 4
code, and entrust the tester to experience, and great
Types of check and challenge this code. communication skills. You must
Game Testing
also be proficient in writing
Techniques Do not deceive yourself into
algorithms to determine
thinking that testing a game
in-game bugs and be able to
merely means playing it. Finding
LVL 5 describe them in detail.
and reporting bugs is much
Bug reporting That said, the QA team usually
contains the highest ratio of
gamers among all departments.
BOSS FIGHT
Most Common
Video Game
Bugs
We test all day
and play games all night!

Copyright 2020 © QATestLab. All Rights Reserved 3

Click the section
to jump ahead TESTING IN THE GAME
DEVELOPMENT
LIFE CYCLE
INTRO
DUCTION

LVL 1
Who are
Game Testers?

LVL 2
Testing in the
Game
Development
Life Cycle

LVL 3
Test
Documentation

LVL 4
START
Types of
Game Testing
Techniques PRODUCT MATURITY TESTING STYLES

Test sympathetically throughout

LVL 5
the earlier development stages,
Concept
Bug reporting as the product is immature and
lacks major functionality. Use
simple tests (such as smoke or
BOSS FIGHT
capability testing) to check
Prototype
Most Common whether the features, as they
Video Game are implemented, are
Bugs
operational.

Copyright 2020 © QATestLab. All Rights Reserved 4

 PRODUCT MATURITY TESTING STYLES
Click the section
to jump ahead Test aggressively in the middle of
the development process, as
Vertical Slice new features get implemented
(a fully playable sample) and are shaken down. Embark
on full-time bug fixing with more
demanding and complex tests.
INTRO
Alpha (carried out by QA
DUCTION Keep executing high-quality
engineers) and Beta (performed
by «real users») Testing testing by diversifying tests near
the end of the project. Get
LVL 1
creative with customized
Who are
Gold Master / Release approaches, automation, heu-
Game Testers?
ristics, beta testers, and so on.

Test meticulously in the final

LVL 2 Post-Launch days before release, examining
Testing in the every change and verifying the
Game correct version of all the files.
Development Game Decommissioning
Life Cycle Keep testing your game as long
(requires extra effort when it
comes to online multiplayer as it exists. Ensure high-quality
games that involve monetization) updates, added functionality,
LVL 3 bug fixes, and performance
Test improvements that are indis-
Documentation pensable for game longevity and
gamer engagement.

LVL 4
Types of
Game Testing
Techniques

Carrying out QA should be placed in the context of the entire

LVL 5 game development life cycle. The time and costs of fixing a bug
increase with each development stage. To gain an appropriate
Bug reporting
level of quality, a range of testing activities should be performed.

 Documentation testing and correction.

BOSS FIGHT  Prototype and Vertical Slice testing.
Most Common  Content testing.
Video Game
Bugs  Alpha and Beta testing preparation and execution,
followed by data collection, processing, and analysis.
 Post-release QA support.

Copyright 2020 © QATestLab. All Rights Reserved 5

Click the section
to jump ahead TEST
DOCUMENTATION
INTRO
DUCTION
TEST PLAN

LVL 1 The testing process cannot operate in a vacuum which is why it

Who are requires a plan. This is the primary means by which QA engineers
Game Testers? communicate their intentions to the game development team.
The purpose of a test plan is to define the scope, approach, resources,
and schedule of the testing process, as well as to identify the tasks to
LVL 2
be performed, testers responsible for each task. and associated risks.
Testing in the In many ways, the process of creating a plan is worth more than the
Game
plan itself, as getting everyone to understand and agree to the
Development
Life Cycle contents of the plan is key.

TEST CASES
LVL 3
Test A test case is an action algorithm executed to verify a particular
Documentation feature or functionality of the product under test. It documents the
values used for input along with the anticipated outputs, as well as
identifying any constraints on the test procedure.
LVL 4
Positive test cases are used to ensure that end-users can perform
Types of
appropriate actions when using valid data. On the other hand,
Game Testing
Techniques negative test cases are conducted to challenge the game by
performing invalid or unacceptable actions, or by using invalid data
(for instance, using an incorrect password for authorization).
LVL 5
Bug reporting CHECKLIST

A checklist is a list of tests required for a product. It helps to keep the

BOSS FIGHT team in the loop about the current state of the testing process, as well
Most Common as to assess the overall product quality.
Video Game Throughout the testing process, the QA engineer marks each item on
Bugs
the checklist according to its status: Passed, Failed, Blocked, In
Progress, Test Not Run, or Skipped.

Copyright 2020 © QATestLab. All Rights Reserved 6

Click the section
to jump ahead TYPES OF GAME
TESTING TECHNIQUES
INTRO
DUCTION
Game testing involves the use of a variety of manual and
automated techniques, identified by the scope of the test.
LVL 1 System analysis for potential vulnerabilities is carried out by a
QA engineer and a potential gamer. The game testing process
Who are
Game Testers? requires implementing some testing techniques not included in
traditional software testing.

LVL 2
Testing in the
Game
Development
Life Cycle

LVL 3
Test
Documentation

LVL 4
Types of
Game Testing
Techniques
BALANCE TESTING involves COMPATIBILITY TESTING is a
making sure that the easy levels technically demanding process
LVL 5 are challenging enough while the intended to ensure that the
Bug reporting harder levels are not too difficult. game is compatible with
For multiplayer games, it verifies multiple hardware
maps are neutral in their design, configurations, such as GPUs,
BOSS FIGHT weapons are equal in power, and RAM modules, or various
spawn points are placed fairly. peripherals.
Most Common
Video Game Game balance is the keystone to
Bugs ensuring winning a game is both
fair and fun.

Copyright 2020 © QATestLab. All Rights Reserved 7

 COMPLIANCE TESTING certifies AD-HOC TESTING is a freestyle
Click the section
to jump ahead that the game follows technical testing type that requires no
standards, system documentation. QA engineers,
documentation is complete, and who are familiar with the
development and design are as product under test, perform
per specifications. random checking and thereby
detect bugs unreachable via
INTRO
structured testing. Put simply,
DUCTION
ad-hoc testing requires naturally
LOCALIZATION TESTING progressing in the game while
LVL 1 involves a thorough check of the trying to be ambushed by an
Who are adaptation and linguistic undetected gang of bugs.
Game Testers? accuracy of the user interface
and in-game content for other
locales. To ensure successful
LVL 2 game localization, a LocKit USABILITY TESTING makes sure
Testing in the (Localization Kit) is needed the gameplay mechanisms,
Game containing tools, instructions, including the user interface, are
Development and resources, including the list consistent, flexible, intuitive, and
Life Cycle
of text blocks translated into comfortable to use. It helps
multiple languages. improve end-user satisfaction,
makes the system highly
LVL 3
effective, and provides insights
Test from a potential target
Documentation
PLAYTESTING involves a audience.
potential target audience trying
LVL 4 out an unfinished project. It
serves to assess the fun factor
Types of
and emotional engagement the FUNCTIONAL TESTING covers
Game Testing
Techniques gameplay creates. Apart from all game mechanics required by
merely playing the game, it also specifications, objects, locations,
includes session preparation, as well as the game engine
LVL 5 controls, and analysis. interactions. For this purpose,
Bug reporting developers create additional
functionality in the code, usually
called cheat codes. A cheat code
BOSS FIGHT allows testing engineers to check
Most Common a specific game location or
Video Game plotline without the need to
Bugs complete quests first.

Copyright 2020 © QATestLab. All Rights Reserved 8

Click the section PERFORMANCE TESTING allows
to jump ahead assessing the maximum
possible technical load on the
system. This testing technique is
essential for video games as it
enables QA engineers to identify
INTRO and fix the most technically
DUCTION challenging areas requiring a lot
of device resources.

LVL 1
Who are
Game Testers? PROGRESSION TESTING is
about playing the game in a
linear way to ensure gameplay is
LVL 2
never interrupted. Progression
Testing in the breaks are often caused by
Game
scripting issues and prevent the
Development
Life Cycle system from responding to
gameplay events, eventually
blocking progress across the
LVL 3 game.

Test
Documentation

SECURITY TESTING involves an REGRESSION TESTING is a

LVL 4 analysis of the game system for crucial part of the testing
Types of any potential vulnerabilities that strategy because functionality
Game Testing could be exploited by cheaters, that used to work may
Techniques and a thorough bug fixing sometimes become broken after
process to guarantee integrity, multiple modifications.
security, and accessibility of the Conducted regularly, regression
LVL 5
gamers’ data. testing confirms the system
Bug reporting seamless operation free from
side effects of new feature
implementation and old bugs in
BOSS FIGHT the current code.
Most Common
Video Game
Bugs

Copyright 2020 © QATestLab. All Rights Reserved 8

Click the section
to jump ahead BUG
REPORTING
INTRO
DUCTION
Bug reporting is the primary way to inform the developers about
the problems that occurred during the testing process. It is a
LVL 1 multifaceted beast requiring a high level of detail regarding the
process the tester used to achieve the outcome, test evidence,
Who are
Game Testers? and associated technical risks.

A bug report usually covers the following: bug description, summary,

background details, steps to reproduce the bug, expected and actual
LVL 2
results, and other relevant information, namely stack traces, test
Testing in the cases, screenshots, error reports, etc.
Game
Development
Life Cycle
THE BEST PRACTICES OF BUG REPORTING INCLUDE:

 Report each bug promptly, but don’t try to fix them.

LVL 3
 Make sure your report is compact, unique, specific about
Test the problem, unambiguous in terms of the flaw severity,
Documentation
and detailed about the bug behavior.

 Remember that the summary is an essential part of the

LVL 4 bug report. A good summary briefly outlines the
Types of information to visualize the failure, indicate its limits, and
Game Testing point out the impact of the bug.
Techniques
 Specify the platform (PC or mobile) as well as the OS type
and version the bug can be reproduced on
LVL 5  Create an easy-to-follow algorithm for the developer to
Bug reporting trigger the bug and reproduce it on their computer.

 Be non-judgmental in your approach and be aware of your

BOSS FIGHT tone as developers will see the reports.

Most Common
Video Game
Bugs

Copyright 2020 © QATestLab. All Rights Reserved 10

Click the section
to jump ahead MOST COMMON
VIDEO GAME BUGS
INTRO
DUCTION
Let’s zoom in a little to observe typical game bugs in their natural
habitat. Chances are, you might be already familiar with what’s
LVL 1 listed here from your experience as a game developer or a gamer.

Who are That said, it is time to deal with it like a testing engineer!
Game Testers?
STABILITY BUGS Examples:
lower the extent to which the Freezes (the system becomes
LVL 2
code behaves according to unresponsive), Crashes (the
Testing in the requirements. They are screen goes dark), and
Game
considered critical because Loading Bugs (a halt in the
Development
Life Cycle they take away any control level loading process).
over a game.

LVL 3 LEVEL-DESIGN BUGS Examples:

Test represent a wide range of Stuck or Sticky Spots (impossi-
Documentation spatial flaws. Of course, ble or requiring time and
sometimes items such as effort to get out), Map Holes
invisible walls and borders (sometimes allow cheating by
LVL 4 are intentional to make the shooting others from under
Types of level seem larger, but the map), Invisible Walls, and
Game Testing experienced testers recognize Missing Geometry (the art is
Techniques
this technique. present but it makes no
barrier to the movement).

LVL 5
Bug reporting AUDIO BUGS, such as volume Examples:
differences, can be easily Audio Drops (especially
detected even by a newbie annoying when happening in
BOSS FIGHT tester. the middle of important
dialogues), Skipping, Distor-
Most Common
Video Game tion, Missing Sound Effects,
Bugs and Volume Level (too loud or
too faint sound effects non-ad-
justable with volume sliders).

Copyright 2020 © QATestLab. All Rights Reserved 11

Click the section VISUAL BUGS are errors Examples:
to jump ahead
affecting a graphical user Clipping (a polygon
interface. They can range penetrates another polygon),
from barely noticeable Z-fighting (overlapping
texture issues to ironclads textures), Screen Tearing,
flying through the air and Missing Textures, and Visible
INTRO leaving floating tracks. Still, Artifacts (small visual glitches
DUCTION regardless of the severity of a of any type, such as speckles
visual bug, they always drive or jaggies).
gamers crazy.
LVL 1
Who are
Game Testers?
ARTIFICIAL INTELLIGENCE Examples:
BUGS, sometimes referred to Pathfinding (an NPC cannot
LVL 2
as artificial stupidity, generate find its way around the map)
Testing in the illogical behavior in and NPC Behavior (NPC
Game
Development non-player characters. teammates are too clumsy
Life Cycle blocking doorways or walking
into walls that undermine the
gamer’s confidence as a grand
LVL 3 commander).
Test
Documentation

PHYSICS BUGS decrease Examples:

LVL 4 the credibility of the game Dynamic Behavior (the
Types of reality. The objects in a objects your character
Game Testing game obey the laws of interacts with do not behave
Techniques physics mainly by according to the basic laws of
rebounding when physics) and Breakables (a
cannoned into or breaking lack of breakable geometry
LVL 5 into pieces — the more when objects break down in
Bug reporting realistically, the better. pieces due to the extensive
damage).

BOSS FIGHT
Most Common
Video Game
Bugs

Copyright 2020 © QATestLab. All Rights Reserved 12

Click the section PERFORMANCE BUGS affect Examples:
to jump ahead
the speed of code processing. Frame Rate (performance
In general, they are the below the frame rate goals),
easiest to spot and hardest to Load Time (long and random
fix. loading times), Minimum
Requirements Machine (the
INTRO game does not run properly
DUCTION on the lowest denominator
machine it should run on),
and Installation Time Bugs
LVL 1
(the game takes too long to
Who are get installed).
Game Testers?

LVL 2
COMPATIBILITY BUGS Examples:
Testing in the
prevent the software from Video Card, Controller,
Game
Development running seamlessly on Operating Systems, and
Life Cycle different hardware, Standards Compatibility Bugs.
operating systems,
network environments,
LVL 3 and mobile devices.
Test Testing game compatibility
Documentation is a complicated task that
requires emphasizing
particular aspects.
LVL 4
Types of
Game Testing
Techniques
NETWORKING BUGS Examples:
negatively affect Failed or Dropped
server-client connectivity Connections (between
LVL 5
and network bandwidth. consoles), Lags (a delay
Bug reporting between the user doing
something and the game
reacting to it) and Scoring
BOSS FIGHT
Errors.
Most Common
Video Game
Bugs

Copyright 2020 © QATestLab. All Rights Reserved 13

Click the section
to jump ahead DON’T LET BUGS
MAKE IT PAST QA
INTRO
DUCTION
When activities are planned, QATestLab is an independent
executed, and reported software testing and QA services
LVL 1 accurately, software testing can provider with extensive
Who are give you knowledge of nearly all experience in all the newest
Game Testers? your game bugs and provide you tools and platforms to skyrocket
with the information and game quality. We provide
support required to fix them. on-demand testing support from
LVL 2 preproduction to the final stages
To achieve maximum quality,
Testing in the of development.
you should choose a testing
Game
Development services provider that meets all In over five years of operation in
Life Cycle your requirements. The benefits this domain, we have
of hiring an independent testing established numerous
team include a structured partnerships with leading game
LVL 3 expert-level testing approach, development companies and
Test test automation, possibility of accomplished multiple projects
Documentation short-term engagements, and within various game genres,
cost reduction when it comes to such as adventures, shooters,
the need to employ specialized strategies, and more.
LVL 4 staff or train your internal team.
Types of
Game Testing
Techniques

Get in touch with us today

LVL 5
to elevate your game
Bug reporting
to new heights with the
BOSS FIGHT
all-conquering power
Most Common of testing.
Video Game
Bugs

Copyright 2020 © QATestLab. All Rights Reserved 14

Click the section
to jump ahead CONTACT
INFORMATION
INTRO
DUCTION
OFFICE IN UKRAINE

LVL 1
Phone: +38 (044) 501-55-48
Who are
Game Testers?
E-mail: [email protected]

LVL 2 Address: 4, Vatslava Havela blvd.,

03142, Kyiv, Ukraine
Testing in the
Game
Development
Life Cycle

COPYRIGHT
LVL 3
Test This guide may be reproduced Although we endeavor to provid
Documentation or copied (partly or entire) in any eaccurate and timely
form or by any means free of information, there is no
charge only with placing link to guarantee that such information
LVL 4
QATestLab is accurateat the time it is
Types of (www.qatestlab.com). received or that it will remain to
Game Testing
be accurate in the future.
Techniques All the information included in
this document can be used only No one should operate on the
for informational purposes. basis of such information with
LVL 5 out appropriate professional
The information contained in
Bug reporting advice after thorough analysis of
this documentis general and is
the particular situation.
not intended to record specific
circumstances of any particular
BOSS FIGHT
individual or organization.
Most Common
Video Game
Bugs

Copyright 2020 © QATestLab. All Rights Reserved