8. QA Workflow

Table of Contents

1. Planning and management
2. Test Plan
3. Tools
4. Bugs reporting

Planning and management

The approach that will be used to work on the project for the best QA workflow will be as follows:

Test Plan

When it comes to testing, the following steps will be taken:

• 1. A test plan will be made for each release, containing all the features to be implemented and the details on how to test them. This plan can be modified during development.
• 2. New features will be tested as they are implemented.
• 3. When reporting:
  • 1. If no problems are found, the feature can be checked in the test plan and marked as "Done" in Trello.
  • 2. In case a bug or problem is found the feature will remain unmodified in and the Trello card will be sent back to the developers as specified in "Planning and management".

Tools

The tools to be used for the defined QA workflow will be the following:

• Discord for communication.
• Google Docs to create the test plan.
• Optick Profiler to profile the game and check performance.

• Trello for proper workflow visualisation.

Bugs reporting

Bugs are an unavoidable part of every programming endeavor. None are planned, and repairing them takes time. Although it is usually difficult to check for each one, it is preferable to find them before it is too late in the production process. Some may simply take time to solve, some will be impossible to deal with, and others will need us to change the game's course and determine how to address them as a group.

Bugs will be reported in Github Issues when releases are tested. Bug reports must adhere to a strict standard and be peer reviewed to ensure that they are clear and understood.

We will be using GitHub's issues tab in order to report bugs so that the developers can check them whenever they appear.

Quality Testing

Quality Tests are made by Ethan Martín, QA tester from the team.

He will follow the steps stated in Test plan