QA Plan - Guille1406/The-Legend-of-Zelda-Hyrule-Conquest GitHub Wiki

##Index

###Stabilization Procedure

There will be 10 releases, and there will be a QA Test for everyone:

v.0.1.X: First release

v.0.7.X: Alpha Release

v.1.0.X: Last release (Gold Version)

There will be a first version of every release (v.0.X.0) without QA Test, and then some versions will be released after QA Tests. First one will be done by QA Lider, and when we get an stabilized version, we get external people to do Play Testing.

###Issue

We gonna use this parametres to make our issues:

####Title

Tiltle that describes the bug.

####Priority

Critical Bug: Bug that prevent continued gameplay or progression. Must be solved in the less time needed, even if the next release has to be delayed.

Exemple:

The game crash.

High Priority Bug: Bug that negatively affect gameplay, but don’t produce crash. It can`t be in the last release.

Exemple:

Collision bug, player can go through objects.

Low Priority Bug: Bug that don’t significantly affect gameplay, and it's difficult to detect.

Exemple:

Objects have a small patch of corrupted or missing graphics.

####Type:

Logic
UI & scenes
Camera
Scripts & NPC
Player
Map & Sound

####Frequency

The frequency the bugs appears.

####Status

Open: Bug founded.
Assigned:Bug assigned by the attendant of the module.
Rejected: Is not bug.
Fixed: Solved?
To be verified: Verify if it's trully solved
Re-Opened: Not solved, cycle again.
Closed: Solved

####Results

Description of the bugs with details.

####Screenshot

If it's needed, a screenshot that show the bug or help to understand the problem.

####Additional Info

Information that helps to solve the bug.

####Issue table

###Play Testing

This is the methodology we gonna use to make the true releases:

Return to Home