HeaderSIS.jpg

IS480 Team wiki:2017T2 Bunanas User Testing

From IS480
Jump to navigation Jump to search


BunanasLogo.png



Team Hei Home.png   HOME

 

Team Hei About.png   ABOUT US

 

Team Hei Overview.png   PROJECT OVERVIEW

 

Team Hei Mgmt.png   PROJECT MANAGEMENT

 

Team Hei Doc.png   DOCUMENTATION

 

Internal Testing User Acceptance Testing 1 User Acceptance Testing 2 (Admin) User Acceptance Testing 2 (Volunteer) User Acceptance Testing 2 (Benficiary)

Objectives & Scope

During every sprint, testing is done on every functionality which has been developed – including those which were implemented in the previous sprints. The objective of regression testing differs from UAT and functional testing. Through regression testing, we will be focusing on problems that arise after the software has been modified, also referred to as software regression. Many factors like changes in common utility services, networking configuration or even user input may be responsible for regression, which is our focus. Alongside, through functional testing, we will be focusing on whether aspects of the software implementation are working to fulfil the project requirements.

To ensure consistency and compatibility of our software implementation, we test our product across multiple systems and platforms:

  • Operating Systems:
    • Windows 10.1
    • macOS Sierra 10.12.6
  • Browsers:
    • Google Chrome
    • Firefox
  • Devices:
    • iPhone 7
    • Oppo A57
    • Samsung S7

Testing Procedure

Quality Assurance (QA) is responsible for the execution of the test plan in every sprint. Our team does not believe that the iteration is fulfilled when functions are implemented, but rather continual testing and maintenance is equally crucial in our efforts to deliver an optimal product. Therefore, our team engages in manual testing in every sprint, which spans from start to end of the iteration.

Testing Lifecycle:

1. Development Phase

Every individual developer conducts local testing as they develop, on the functionalities they are assigned. Concurrently, Quality Assurance constructs test cases for all functions being developed in the currently sprint, to stress test the product.

2. Initial Testing

Quality Assurance works alongside the respective developers to test the functions against the test cases. All bugs found are recorded into the Bug Log document. Respective developers debug the functions which they are assigned, starting from the most severe bugs. Quality Assurance verifies, through testing against test cases again, that known bugs have been resolved.

3. Staging Server

After all known bugs are resolved, application is hosted on staging server for regression testing. Quality Assurance carries out regression testing against all past test cases. Like before, all bugs found in this stage is also logged onto the Bug Log document. Respective developers debug known bugs and Quality Assurance verifies.

4. Production Server

After all known bugs are resolved, software implementation is pushed to production server, where Quality Assurance conducts last round of regression testing. All bugs found are documented and worked on by respective developers like before. After so, testing documentation is finalized and uploaded to wiki.
Should there be deviations and delay in debugging, Quality Assurance will report and discuss with Project Manager with regards to development cycle, and severity of the bug. If the bug is major, Project Manager will decide to halt all oncoming development work, till another round of debugging and testing is done. Minor bugs can be covered, and debugged during the next debugging session of the following sprint.