HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 Can.One Testing"

From IS480
Jump to navigation Jump to search
Line 18: Line 18:
 
<font face="century gothic" size="2">
 
<font face="century gothic" size="2">
  
===<div style="color: #ffffff; font-size:0%">Usability Testing 1</div>===
+
===<div style="color: #ffffff; font-size:0%">User Testing 1</div>===
 
{| class="wikitable" cellpadding="15"
 
{| class="wikitable" cellpadding="15"
 
|-
 
|-
| style="background:#ffffff;; color: #800000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:left; border: 1px solid #ffffff" valign="top" | <b>Usability Testing 1</b>
+
| style="background:#ffffff;; color: #800000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:left; border: 1px solid #ffffff" valign="top" | <b>User Testing 1</b>
 
|-
 
|-
  

Revision as of 01:37, 21 February 2013

Home Project Overview Project Management Project Documentation Testing Learning Outcome

User Testing 1

User Testing 1

Date: 18-19 January 2013

Location: SEIL Lab

Objective:

  1. Observe how users interact with our application
  2. Collect feedbacks from users regarding application’s usability


Scope Tested:

  • Registration & Login
  • Create & Display Avatar
  • Add Accessories to 3D Avatar
  • Profile Page
  • Shopping
    • Shopping Cart
    • Payment Gateway
    • Promotions
    • Rewards
  • Social
    • Friends
    • Chat
    • Groups


Testers: 30 people (young adults, age 15-25)

- Sze Ming and Jin Yao
- 14 male and/or female age 15-20
- 14 male and/or female age 21-25


Testing Methodology
There will be 3 x 45 minutes of test section each day. 5 testers will concurrently test the application in each section. Testers will be given a task list that will involve completing activities based on the tested functionalities. They are encouraged to think aloud, while Can.One members observe and note down testers' opinion and behavior when using the web application.

We need to ensure that at least 75% of the testers (22 people) will come again for UAT 1. Therefore during UT 1, testers will be given [$2 worth of item] and a $5 voucher that can be redeemed if they come for UAT 1

During the test, we will collect the following metrics:

  1. Error rate - Using screen recording software, we will see if a task is completed with ease or if a task is only completed after many wrong turns.
  2. Time spent on a task - Using a time clicker, we record the completion time of each task.
  3. Task or test level satisfaction rate - After completion of each task, testers are to fill an online survey that will record their demographics, as well as their feedbacks on each task and the application in general.


Documents:


Usability Testing 2

Usability Testing 2

Date: Beginning of March

Objective:

  1. Observe how users interact with our application
  2. Collect feedbacks from users regarding application’s usability


Scope: TBA

Testers: People who match VEON’s target user profile (young adults, age 15-25)

Testing Methodology
Testers will be given a task list that will involve completing activities based on the tested functionalities. They are encouraged to think aloud, while facilitators are there to help and observe.

During the test, we will collect the following metrics:

  1. Error rate - Using screen recording software, we will see if a task is completed with ease or if a task is only completed after many wrong turns.
  2. Time spent on a task - Using a time clicker, we record the completion time of each task.
  3. Task or test level satisfaction rate - After completion of each task, testers are to fill an online survey that will record their demographics, as well as their feedbacks on each task and the application in general.


Users Acceptance Test

Users Acceptance Test

Date: Beginning of April

Objective: Determine if users find our application intuitive enough, and can navigate without instructions.

Scope: TBA

Testers:

  • Gamurai
  • People who match VEON’s target user profile (young adults, age 15-25)


Testing Methodology
Testers will be given a task list that will involve completing activities based on the tested functionalities. Facilitators will only observe, no guidance and instruction steps will be provided.

During the test, we will collect the following metrics:

  1. Error rate - Using screen recording software, we will see if a task is completed with ease or if a task is only completed after many wrong turns.
  2. Time spent on a task - Using a time clicker, we record the completion time of each task.
  3. Task or test level satisfaction rate - After completion of each task, testers are to fill an online survey that will record their demographics, as well as their feedbacks on each task and the application in general.