HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 31: Line 31:
 
<br>
 
<br>
 
'''Location:''' SIS CR 3.2 (Day 1) & SIS SR 3.2 (Day 2)
 
'''Location:''' SIS CR 3.2 (Day 1) & SIS SR 3.2 (Day 2)
<br>
+
<br>
 
<br>
 
<br>
 
'''Objective:'''   
 
'''Objective:'''   

Revision as of 01:42, 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: SIS CR 3.2 (Day 1) & SIS SR 3.2 (Day 2)

Objective:

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


Scope Tested:

  • Registration & Login
  • Avatar Creation
  • Shopping
    • Try-on Product
    • Add Item to Cart
    • Check Out
    • Payment Gateway
  • Search Friend


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


Testing Methodology

  • 5 testers will concurrently test the application in the chosen time slot (@ ±30 minutes)
  • When arrived, testers will need to sign a consent form and complete a pre-test questionnaire
  • Testers will be given a task list to be completed. For each task, they need to indicate the completion status (pass/fail), the difficulty level (low, medium, high), and comment for the tested functionality.
  • Testers are encouraged to think out loud. Each tester will be closely observed by an observer, who will take notes of tester’s behavior and comment.
  • Upon completing the test, testers will need to complete a post-test questionnaire and subsequently get 2 Subway cookies as a reward


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. Perceived difficulties of each task
  3. Comments regarding any features or the application



Documents:


Usability Testing

Usability Testing

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.


User Acceptance Test

User 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.