QA Plan - AleixBV/StarCraft GitHub Wiki

In this page we will determine how the QA section will work, how we classify the bugs and how we'll fix them

###Index

[Stabilization procedure] (https://github.com/AleixBV/StarCraft/wiki/QA-Plan#stabilization-procedure)

[Bug Classification] (https://github.com/AleixBV/StarCraft/wiki/QA-Plan#bug-classification)

[PlayTesting] (https://github.com/AleixBV/StarCraft/wiki/QA-Plan#playtesting)

[HOME] (https://github.com/AleixBV/StarCraft/wiki)

###Stabilization procedure #####How stabilization will happen in Starcraft: Last Hope

  • We will start in v0.1.0.0
  • Prototype will be v0.5.0.0
  • Final release will be v1.0.0.0

The meaning of this is:

  • First number is for major updates.
  • Second number is for minor updates. e.g. When the fog of war is implemented
  • Third number is for revision updates. e.g. Changes in console module
  • Fourth number is for build number. e.g. Any commit

Return to [index] (https://github.com/AleixBV/StarCraft/wiki/QA-Plan#index)

###Bug Classification In Starcraft: Last Hope we'll classify the bugs by priority. When the priority is determined, bugs will be classified by types. The priority order will be the next one:

  • Critical bug

    Bug that prevent continued gameplay or progression. Examples of this kind of bug can be the following:

  • Bug that prevents the tester to do the testing

  • Bug that requires the user to restart the app

  • High priority bug

    General bug that negatively affect gameplay, but don’t produce crash. Examples of this kind of bug can be the following:

  • Missing sounds effects or music

  • Collision bugs where the 3D object can pass completely or mostly through another object

  • Objects have missing, incorrect or corrupted graphics

  • Low priority bug

    Bug that don’t significantly affect gameplay, and is difficult for the average consumer to notice or detect. One example of this kind of bug is:

  • Objects have a small patch of corrupted or missing graphics.

These are the type of bugs that will be classified:

  • Crash
  • Gameplay
  • UI
  • IA
  • Collision
  • Graphics
  • Sound
  • Text

To notify the bugs to the development team, we will use the following table.

Repro_case

This table should be accompanied by a screenshot of the bug.

Return to [index] (https://github.com/AleixBV/StarCraft/wiki/QA-Plan#index)

###PlayTesting In this section we will explain how we will do the tests in the different stages of Starcraft Last Hope. All the tests will be done every major update.

  • Pre-production

    The tests will be directed testing(test cases) and their duration will be around 15 minutes. Directed testing is done when the development team has specific areas or features of the game that they want the testers to focus on. In order to achieve that, in pre-production stage, the member of the team doing the tests will be the QA lead. The goal of this test is to complete each action that is requested by the development team. In the following chart, we will determine how the process in pre-production stage will be done.

    LINK

pre_flow

  • Alpha

The tests will be directed testing and their duration will be around 30-45 minutes. In contrast with the pre-production stage, in Alpha stage, all the team will be doing the tests. The goal of this test is the same as in the pre-production stage, complete each action that is requested by the development team. In the following chart, we will determine how the process in Alpha stage will be done.

LINK

alpha_flow

  • Beta

The tests will be exploratory testing and their duration will be around 45-60 minutes. With this method of testing, the testers will not be guided by the production team. This is the best method to catch bugs that are unseen by programmers. Many bugs are discovered by the unpredictability and diversity of testers play styles. In this stage, the testers will be external players of the production team. The production team can give tips when performing the exploratory testing. e.g.

  • Try to "break" the game
  • Unconventional play style
  • Use everything everywhere
  • Minimize actions
  • Maximize actions

This is the flow chart of the process in Beta stage.

LINK beta_flow

Return to [index] (https://github.com/AleixBV/StarCraft/wiki/QA-Plan#index)