diff --git a/Module Three Project Log - Team Development: QA and Testing Plan.md b/Module Three Project Log - Team Development: QA and Testing Plan.md index 46a2ec5..ff7bd02 100644 --- a/Module Three Project Log - Team Development: QA and Testing Plan.md +++ b/Module Three Project Log - Team Development: QA and Testing Plan.md @@ -60,7 +60,7 @@ In your plan, be sure to include the following: ## **What items will be tested? Include a checklist of items to be tested (pass/fail):** ## ### **Alpha Test Stage:** ### -* **Player Keybinds:** +* **Player Keybinds:** (**Joe Rafferty**) * Press W, Player moves forward * Press S, Player moves backward * Press A, Player moves left @@ -73,60 +73,60 @@ In your plan, be sure to include the following: * Press TAB, task list toggles * Press 1, 2, 3 to toggle between ammo types * Press H to use Health Pickup -* **Jump Pads:** +* **Jump Pads:** (**Brigitte Rollain**) * Jump Pads launch character into the air. -* **Platforms:** +* **Platforms:** (**Daniel Noel**) * Player can reach each platform -* **Capillaries:** +* **Capillaries:** (**Brigitte Rollain**) * Player cannot move through unless crouched * Player can move all the way through while crouched -* **Acid Pools:** +* **Acid Pools:** (**Brigitte Rollain**) * Ensure collision does not prevent player from entering acid pools -* **Hazmat Suit:** +* **Hazmat Suit:** (**Jenji Sayre**) * Item disappears from scene upon pickup -* **Health Pickup:** +* **Health Pickup:** (**Jenji Sayre*) * Item disappears from scene upon pickup -* **Virus Sample:** +* **Virus Sample:** (**Jenji Sayre**) * Item disappears from scene upon pickup -* **Scene:** +* **Scene:** (**Daniel Noel**) * All 5 required rooms are in level * All rooms can be accessed by player -* **HUD:** +* **HUD:** (**Kylie Nencetty**) * Displays task list, Virus sample icons, Hotbar icons, and Health bar -* **HUD: Task List:** +* **HUD: Task List:** (**Kylie Nencetty**) * Updates task list with player progression as expected -* **HUD: Virus Sample:** +* **HUD: Virus Sample:** (**Kylie Nencetty**) * Icons are Grey when sample collection is incomplete * Icons are colored when sample collection is complete * Icons display a ring around them when vaccine has been created -* **HUD: Hotbar:** +* **HUD: Hotbar:** (**Joe Rafferty**) * Icons are grey if vaccines have not been created * Icons are colored when vaccine has been created -* **HUD: Health bar:** +* **HUD: Health bar:** (**Joe Rafferty**) * Changes correctly in relation to health percentage -* **Crafting Station:** +* **Crafting Station:** (**Joe Rafferty**) * Is able to be interacted with ### **Beta Test Stage:** ### -* **Player Keybinds:** +* **Player Keybinds:** (**Joe Rafferty**) * Press H, Health pickup (Time Permitted Function) -* **Acid Pools:** +* **Acid Pools:** (**Kylie Nencetty**) * Applies damage to player over time -* **Hazmat Suit:** +* **Hazmat Suit:** (**Daniel Noel**) * Reduces damage from virus * HUD health bar changes aesthetically after pickup of hazmat suit * Player model's arms have a slightly different appearance to signify hazmat suit has been collected * After picking up hazmat suit, HUD receives a slightly darker view to signify that player is now looking through a mask -* **Health Pickup:** - * Restores percetage of health upon pick up -* **Virus Sample:** +* **Health Pickup:** (**Jenji Sayre**) + * Restores percentage of health upon pick up +* **Virus Sample:** (**Joe Rafferty**) * Damages player if in close proximity without hazmat suit * Kills player upon pickup if hazmat suit has not been collected -* **Information Screen:** +* **Information Screen:** (**Kylie Nencetty**) * Ensure all tabs are clickable * Ensure all tabs switch to intended widget * Ensure all tabs meet predetermined design requirements -* **AI:** +* **AI:** (**Joe Rafferty**) * Viruses are reproducing * Virus reproduction type is random * Virus reproduction limit of 20 @@ -135,52 +135,52 @@ In your plan, be sure to include the following: * Beta virus moves at slow moving pace * Gamma virus floats and moves around environment * Viruses do not clip through environment -* **Crafting Station:** +* **Crafting Station:** (**Joe Rafferty**) * Verify vaccine is created for only viruses of which all samples have been collected. * Crafting widget appears on screen (Time Permitted Function) -* **Craftable Vaccines:** +* **Craftable Vaccines:** (**Brigitte Rollain**) * Alpha vaccine only destroys Alpha Virus * Beta vaccine only destroys Beta Virus * Gamma vaccine only destroys Gamma Virus -* **End of Game:** +* **End of Game:** (**Kylie Nencetty**) * First level completed widget appears when all viruses have been eliminated * Game over widget appears when player loses 100% of health * Play Again button resets level (on both widgets) -* **Projectiles:** +* **Projectiles:** (**Daniel Noel**) * Projectile fires as expected (i.e. path, direction, velocity) -* **Viruses:** +* **Viruses:** (**Jenji Sayre**) * Player takes damage within proximity of viruses -* **Health Damage:** +* **Health Damage:** (**Jenji Sayre**) * Upon player taking damage health is reduced ### **Code Release Test Stage:** ### -* **Alpha Tests:** +* **Alpha Tests:** (**Group Decision**) * Run through Alpha tests again -* **Beta Tests:** +* **Beta Tests:** (**Group Decision**) * Run through Beta tests again -* **Textures, Materials, & Models:** +* **Textures, Materials, & Models:** (**Jenji Sayre**) * Ensure all assets are implemented correctly with appropriate textures/materials * Ensure aesthetics are displaying as expected ----------------------------------------------------------------------------------------------------------------- ## **How will you update the test plan to reflect changes to the game and design document?** ## -* Updates will be notated in the designated Test Plan Document and the traceability matrix when applicable. -* The importance/necessity of any changes or features will be evaluated as a team. - * We will then determine, as a team, which phase any changes need to be implemented and tested. +* Updates will be notated in the designated Test Plan Document and the traceability matrix when applicable. (**Group Decision**) +* The importance/necessity of any changes or features will be evaluated as a team. (**Group Decision**) + * We will then determine, as a team, which phase any changes need to be implemented and tested. (**Group Decision**) ----------------------------------------------------------------------------------------------------------------- ## **How will bugs be reported?** ## -* Bugs will be reported using the issue tracker within Bitbucket. - * Within the issue tracker, the bug will be assigned to the appropriate team member to resolve. - * Once resolved, the assigned team member will change the issue to resolved within the issue tracker. +* Bugs will be reported using the issue tracker within Bitbucket. (**Group Decision**) + * Within the issue tracker, the bug will be assigned to the appropriate team member to resolve. (**Group Decision**) + * Once resolved, the assigned team member will change the issue to resolved within the issue tracker. (**Group Decision**) ----------------------------------------------------------------------------------------------------------------- ## **How will the bugs and their changes be tracked over time?** ## -* As previously mentioned, bugs will be tracked over time using the issue tracker in Bitbucket. - * Once a bug is resolved, it will be marked as resolved within the issue tracker. -* Also previously mentioned, we will be recording bugs and their changes using a Google Docs sheet. This sheet is formatted as an Excel document. The sheet contains a traceability matrix, and separate pages for each stage of testing (Alpha, Beta, and Code Release). All team members will be able to edit these sheets. We can record test results here as well as changes that were made to resolve bugs. +* As previously mentioned, bugs will be tracked over time using the issue tracker in Bitbucket. (**Group Decision**) + * Once a bug is resolved, it will be marked as resolved within the issue tracker. (**Group Decision**) +* Also previously mentioned, we will be recording bugs and their changes using a Google Docs sheet. This sheet is formatted as an Excel document. The sheet contains a traceability matrix, and separate pages for each stage of testing (Alpha, Beta, and Code Release). All team members will be able to edit these sheets. We can record test results here as well as changes that were made to resolve bugs. (**Group Decision**) ----------------------------------------------------------------------------------------------------------------- \ No newline at end of file