Difference between revisions of "IS480 Team wiki: 2012T1 6-bit Project Management UT2"
Line 171: | Line 171: | ||
====Test Procedures==== | ====Test Procedures==== | ||
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!. | Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!. | ||
− | Subsequently, they are provided with an instruction sheet for a guided test experience. Testers will be required to perform a series of system tasks based on a test case that will go through all the system features and use-case. Thereafter, testers will | + | <br><br> |
− | + | Subsequently, they are provided with an instruction sheet for a guided test experience. Testers will be required to perform a series of system tasks based on a test case that will go through all the system features and use-case. Thereafter, testers will fill in details in an open-ended textbox appended after each question, should they encounter any bugs or suggestions for improvements. | |
+ | |||
====Test Instruction==== | ====Test Instruction==== | ||
[https://dl.dropbox.com/u/56071797/User%20Testing%201%20Instructions.docx Click Here to Download User Testing 1 Instruction] | [https://dl.dropbox.com/u/56071797/User%20Testing%201%20Instructions.docx Click Here to Download User Testing 1 Instruction] |
Revision as of 23:00, 1 December 2012
by offering a place for exchanging ideas and information on its public domain.
http://www.chapalang.com
Final Wikipage |
Home | Technical Overview | Project Deliverables | Project Management | Learning Outcomes |
Schedule
Planned Schedule
Meeting Minutes
Team Meeting Minutes
Supervisor Meeting Minutes
|Meeting Minute 1
|Meeting Minute 2
|Meeting Minute 3
|Meeting Minute 4
|Meeting Minute 5
|Meeting Minute 6
|Meeting Minute 7
|Meeting Minute 8
|Meeting Minute 9
|Meeting Minute 10
|Meeting Minute 11
Testing
Test Cases
Test Plans
Test Plan 1 on 17 September 2012
Test Plan 2 on 28 September 2012
Test Plan 3 on 19 October 2012
Test Plan 4 on 4 November 2012
User Testing
User Testing 1 | User Testing 2 | User Testing 3 | User Testing 4 |
User Testing 2
Test Description
The objective of User Test 2 is on functionality and usability testing of the system. The coverage of the test is focused on forum and basic marketplace functions.
The purpose of re-testing on forum function is to test for an experience improvement. Basic marketplace functions will consist of a complete product display to payment process. We will want to find out if the changes made after User Test 1 is offering an improved user experience to users, and whether the improvement is consistent between forum and marketplace functions.
Testers Background
There are a total of 46 testers who attended the User Test, of which 61% (28) are male and 39% (18) are female, representing various schools in SMU with SIS students being the majority. It is also observed that most testers are users of Chrome and Firefox web browser.
There is no significant difference between testers’ background in User Test 1 and 2.
Test Groups
There are 2 test groups employed in this test.
Group A (Control Group) consists of 17 testers who were testers from User Test 1. The purpose is to test if their return experience with the system has any improvements.
Group B (Test Group) consists of 29 new testers who have not participated in any of our previous user tests. The purpose of their participation is for comparison, to find out if they have a different experience from the returning testers in Group A.
Test Procedures
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!.
Subsequently, they are provided with an instruction sheet for a guided test experience. Testers will be required to perform a series of system tasks based on a test case that will go through all the system features and use-case. Thereafter, testers will fill in details in an open-ended textbox appended after each question, should they encounter any bugs or suggestions for improvements.
Test Instruction
Click Here to Download User Testing 1 Instruction
Test Results
Based on the abovementioned set of results, it is reasonable to conclude that the system is above satisfactory on functionalities for most testers while there are some rooms for improvements especially on intuitiveness.
There are also 4 reported bugs, and 19 recommendations for improvements received.
The top 10 most frequently mentioned or important recommendations will be published and appended below.
Click Data Analysis
Additionally, click data of each test session has also been collected and analysed.
Based on the computed statistics illustrated in the box-plot above, the median number of clicks it takes per tester to accomplish a task ranges from 1 to 8 clicks, with 3 clicks being the median. For the purpose of understanding, we could take the measurement of 3 clicks per task as a benchmark, to be compared on subsequent test sessions and observe if there are any improvements.
More statistics were computed in the box-plot diagram above to understand the median time spent to accomplish a task and we observe that the time taken ranges from 4 seconds to 18 seconds, with 10 seconds being the median. We will also be taking the measurement of 10 seconds per task as a benchmark to compare with subsequent test sessions and observe if there are any improvements.
Additional Observations
Further drill down on the click data has identified an observation where most testers take more clicks to accomplish Step 4 of the instructions. In Step 4, testers are required to subscribe a forum. In this observation, we are able to relate that testers are unable to easily find the Subscribe to Forum button. This finding is aligned with a common feedback that we should consider replicating the subscription button to a more intuitive location on the webpage.
Milestones
Schedule Metric
Bug Metric
Bug Log: |Click Here