HeaderSIS.jpg

IS480 Team wiki: 2016T1 CLEBS DOCUMENTATION TEST

From IS480
Jump to navigation Jump to search
ClebsLogo.png
ClebsHome.png HOME

ClebsAboutUS.png THE TEAM

ClebsProjectOverview.png PROJECT OVERVIEW

ClebsProjectManagement.png PROJECT MANAGEMENT

ClebsDocumentation.png DOCUMENTATION

  T E C H N I C A L   D O C U M E N T S  

  D E S I G N  

  Q U A L I T Y   A S S U R A N C E  

  M E E T I N G  M I N U T E S  

  I S 4 8 0   D E L I V E R A B L E S  

User Test 1 User Test 2 User Test 3 User Test 4


User Test 1 Test Plan

Date: 27 July 2016, Wednesday
Venue: At participants' convenience
Duration: 10 – 20 minutes per participant
Number of Participants: 12
Age range: 19 – 26



Objectives:

  1.   Identify functionalities and usability issues
  2.   Determine is the user interface is intuitive
  3.   Discover ways to improve features and functions of the website based on the results of User Testing #1




Scope:
The scope for User Testing 1 are the modules from sprints 1 - 3

  1.   Registration Module
    • Log In
    • Log Out
    • Registration
  2.   Profile Management Module
    • Update Profile (including upload profile picture)
    • Reset Password (Shifted to sprint 5)
    • Change password
  3.   Project Proposal Module
    • Submit Project Proposal
  4.   User Management Module
    • View All Users
    • Ban Users
    • Un-ban Users




Procedure:

  1.   A test plan with instructions on how to test the website have been given to the testers
  2.   Participants will log down the testing outcomes in the sheet
  3.   Participants are welcomed to type their general comments and feedback into the feedback textbox provided at the end of the test plan document




Tasks:
The test plan consisted the following five tasks:

  1. Registration
  2. Login
  3. Update Profile
  4. Submit Project Proposal
  5. Administrative Features – Create/Remove Administrator Accounts, Ban/Unban Users


For every task, participants were required to document down the following information:

  • Execution of Task (Successful or Unsuccessful)
  • Outcome
  • Level of Difficulty (Scale of 1 - 5)


At the end of the test plan, we also asked the participants the following questions:

  • What do you like about the website?
  • What do you dislike about the website?
  • Are there any other areas of the website that you would like us to improve on?


Objectives and Results

In User Testing 1, our objectives are for participants to be able to complete the tasks with ease, without asking for assistance from the team.

S/N Objective Achieved? % of Participants that found this task easy or very easy
1 Participants should be able to register for an account Yes 100%
2 Participants should be able to login Yes 100%
3 Participants should be able to update their user account Yes 100%
4 Participants should be able to submit a project proposal Partially 66.67%
5 Participants should be able to create/remove an administrator account Yes 91.67%
6 Participants should be able to ban/unban a user account Yes 100%
Percentage of participants who completed all the tasks: 100%


Bug Related Metrics
Total Bug Score: 26
Category of Bugs Number of Bugs
Critical 0
High 4
Low 6
# Description of Bugs Severity Bug Score
1 The side menu does not appear when clicked sometimes High 5
2 Radio button for project type not working when creating project proposal High 5
3 User is able to edit first name, last name and email High 5
4 Amazon Web Service secret keys are publicly visible High 5
5 Log in link at the top right hand corner is not working Low 1
6 After administrator adds a new administrator account, the page redirects to ‘Manage Users’ instead of ‘Manage Administrators’ Low 1
7 Validation for Project Title when submitting a new project proposal is not working Low 1
8 Validation for Project Description when submitting a new project proposal is not working Low 1
9 Validation for contact number when submitting a new project proposal is not working Low 1
10 Profile picture size is not standardize Low 1


Key Findings


Users' Likes

  • The website has a very clean and modern design
  • The website is intuitive
  • Most of the font size is very large, readability is good




Overall Findings Summary
With the user testing 1 results, we have consolidated the problems and issues (qualitative analysis) that participants have encountered during the testing and come up with possible improvements to be made before user testing 2.

Overall Findings Summary
Qualitative Analysis Administrative and user dashboard page does not match the theme of the public pages
Create project proposal does not have a back button
Needs more validation on client side (i.e. Let users know what is invalid after the focus leaves the input elements)
Some pages have too much white spaces, making them look very plain and unattractive
Some pages require a lot of scrolling due to long forms and layouts
Some of the fonts on the pages can become very small, making them hard to read
Some of the words (colours) on the pages are light, which also makes them harder to read on white backgrounds
It is easy to edit other users’ profiles (little to no security in place)
On-screen descriptive messages are not shown for update profile action
Possible improvements to be made before User Testing 2 Redesign the user interface for administrator and user dashboard to complement the public pages’ design
Maximise the page space by rearranging the page elements
Standardise the navigation bar for administrator and user dashboard
Include more necessary validations for the different forms
Include more navigation buttons for improved intuitive user interface
Client-side form validation (before clicking submit button)
Email verification before logging in for the first time
Only allow social media username as input instead of the full hyperlink
Increase the sizes of fonts for better readability (for the benefit of users)
Choose a font colour (even for placeholders and form helpers) that stands out more to engage users
Secure individual users’ profile by preventing access from other users’ accounts
Secure individual users’ password change page by preventing access from other users’ accounts
Have more on-screen descriptive messages to notify when an action is successful or unsuccessful