In this section of Quality Assurance Plan, are explained the milestones QA protocols, the tools that will be used, the process to report correctly a bug and the workflow that will be used.

• Tools Used
• Bug Report Process
• Bug Report Parameters
  • Template
  • Label Parameters
• Workflow Used
• Milestones
  • Internal Milestones
  • Extrenal Milestones

We will be working with GitHub issues in order to report the bugs.

Once found a new bug, the steps to follow are:

• Go to the Issues section.

• Press the “New issue” button.

• Fill the provided template and add the corresponding label to the issue.

• Title: few words to identify the bug.
• Description: brief explanation about the bug.
• Type:
  • A (crash): The game freezes completely or it closed so the player cannot progress.
  • B (severe): Hinders any further progression from the player.
  • C (general): Does not hinder any further progression but it still affects the gameplay.
  • D (minor): Does not significantly affect the gameplay.
  • E (cosmetic): Aesthetic, graphical or audio error. Does not affect gameplay.
• Severity:
  • Critical: Needs to be fixed immediately.
  • High: Needs to be fixed after there are no critical bugs.
  • Medium: Needs to be fixed after there are no high bugs.
  • Low: Needs to be fixed after there are no medium bugs.
• Expected behavior: brief description about what was supposed to happen.
• Actual behavior: brief description about what happened.
• Steps to follow: necessary steps to reproduce the bug.

When a new bug is found, we will follow this process:

We are going to do a weekly build on Saturdays, and on Sundays, the entire development team will do a QA testing session during 45 to 60 minutes to find as many bugs as possible. Then, we will proceed to solve all the bugs we can, giving priority to the ones with higher severity. At the end of the day, we will upload a release on GitHub.

The week before each delivery (Vertical Slice, Alpha, and Gold), an external QA playtesting session will be made for players that do not form part of the development team. This will help to find new bugs and also to receive feedback, so the game can be improved with the goal to make it funnier and more enjoyable.