HeaderSIS.jpg

IS480 Team wiki: 2016T1 Ingenium Testing

From IS480
Jump to navigation Jump to search
Ingenium-logo.png

Home-icon.png Home

Team-icon.png About Us

Overview-icon.png Project Overview

Mgmt-icon.png Project Management

Doc--icon.png Documentation

Technical Diagrams Testing Documents Milestone Documents


Go to: Internal Testing || General Test Plan || UAT 1 Functional Testing || UAT 2 (---)

General Test Plan

Purpose

  • Gather feedback on functionality usability
  • Ensure functionalities are working
  • Modify UI to suit end-user needs
  • Get feedback on the value-add of each functionality
  • Get feedback on potential improvements on each functionality and/or more features for value-add or Quality of Life.


Types of Testing

Testing is broken down into 3 main components, with each User Testing focusing on one of the 3. This is to reduce the average length of each user testing as our end-users find it difficult to do testing for extended periods of time as well as to better focus the feedback given from each user testing.

Functional Testing

  • Manual testing performed at the end of each iteration to ensure the quality of developed functions and it is working as designed
  • Gives users an example of how they would use the system to accomplish their tasks
  • Gather feedback on usability of each function as well as the value-add each function gives to the users. (Does the end-users want to use the function in the way it is currently designed?)

The primary aim of Functional testing is to check the current implemented functionalities whether they are working as planned and whether the end-users are using it without trouble. Functional testing is meant to identify any issues with the implemented functionalities in terms of usability, accuracy, or other factors that may dissuade end-users from using the particular functionality and to correct it.

Integration Testing

  • Manual testing to ensure that the newly developed modules work together
  • Regression testing to ensure that earlier functions are not broken
  • Ensure transitions between functions are smooth and bug-free
  • Allows users to explore using the system as an entire functional system
  • Get feedback on the current transitions between functionalities and system responsiveness

The primary aim of Integration testing is to give users a chance to maneuver the system as is intended for the final product to ensure all integrated functionalities work together without issues occurring. It is also to get feedback from end-users on how they wanted the integrated system to function, so as to better fit the system to the end-users’ expectations.

User Interface Testing

  • Checks with user to ensure critical functions are easily accessed
  • Ensure all interface are displayed as designed bug-free
  • Get feedback on interface design and placement of specific inputs/outputs

The primary aim of User Interface testing is to get feedback on the current design of the system along with some of their frustrations with the new design, if any. User interface testing is meant to check whether the current design is acceptable to the end-users and made adjustments as necessary.


User Testing Process

Users will be given a series of tasks to complete if it’s a functional or integration testing, which users are required to go through all the functionalities to complete the tasks. Users are allowed to give feedback at any point during the test, and are encouraged to check out the application at their leisure. Ideally each member would observe one user, with one member writing the notes and feedback.

Points to note of:

  • Any issues or problems encountered by any of the users
  • Feedback given during test on what task they’re doing
  • Workarounds/bugs they’ve discovered
  • Things that users talked out loud about while doing any particular tasks