“The systematic process of checking to see whether a product or service being

developed is meeting specified requirements”.

INDEX

• PURPOSE

• GLOSSARY

• BUG HIERARCHY

• ORGANIZATION

• TESTING PROCESS

• PRE-ALPHA

• ALPHA

• BETA TO GOLD

• FLOW CHART

PURPOSE

The main goal in our QA department will be to make sure that our game meets certain

standards in order for it to be considered a decent quality game when the gold is released.

GLOSSARY

We will use certain abbreviations or specific vocabulary in order to economize the

communication. Ex: Bug, sprite, NPC, rattata, charmeleon, dragonite (bug categories), etc.

BUG HIERARCHY

• Rattata: Bug that doesn’t affect gameplay at all and is difficult for the player to detect

(trivial). Ex: A certain frame in a NPC animation is inverted.

• Charmeleon: General bug that affects gameplay significatively. It does not produce a

crash. Ex: Certain collision tile does not match the sprites correctly.

• Dragonite: Bug that causes the game to crash or prevents the intended gameplay

progression. Ex: Game crash, softlock, etc.

ORGANIZATION

Our QA manager will be Albert Llopart. We will set our goals and standards so we can manage

our pre-stablished QA testing periods before every release. Every one of us will collaborate

under Albert’s guidance.

TESTING PROCESS

The basic workflow will consist on testing, finding and reporting new issues. When finding an

issue, the tester will use the “issues” tool in github in order to report the bug. A clear title and

an understandable description will be required in order for the developers to be able to

understand, recreate and fix the issue. This should be supported by either a screenshot or a

video if necessary.

The fixes of each bug will be implemented in the new build and the testers will check if it has

been successfully corrected. Then the process will start over again.

WORKFLOW

PRE-ALPHA

Our pre-alpha testing will be a lot UI oriented since it needs to be completed before the alpha

version of the game. Also we’ll make sure that every mechanic / feature added so far is as solid

as possible.

ALPHA

Before the alpha release we’ll make sure that every mechanic and feature is correctly

implemented and working as intended, since from now on we’ll focus on polish and details.

For this purpose, we will stablish a QA period several days before the release to make sure our

objectives are fulfilled. It is known that once you enter alpha phase you cannot implement new

functionalities, so we will focus on making sure that everything we need is implemented and it

is solid.

BETA TO GOLD

This will be our polish period, so testing won’t be so specific or mechanic oriented. We will

look for real users that will test the game (with actual gameplay) so we can get minor glitches

to be fixed before final release. It will be all about polish and details. Again, several days before

release we will stablish a QA period to make sure our goals are accomplished.

FLOW CHART