Difference between revisions of "IS480 Team wiki: 2013T2 LittleTeam ProjectDocumentation Testing"
Jump to navigation
Jump to search
Qian.ye.2011 (talk | contribs) |
Qian.ye.2011 (talk | contribs) |
||
Line 180: | Line 180: | ||
|- | |- | ||
− | ! scope="col" width="550" style="background: | + | ! scope="col" width="550" style="background:blue; color:white"|Generally the system is hard to use for the first time user. Quite a few unnecessary pages and icons. |
− | ! scope="col" width="550" style="background: | + | ! scope="col" width="550" style="background:blue; color:white"|UI Revamp seems necessary, but need to further discuss with client and supervisor |
|} | |} |
Revision as of 01:05, 26 February 2014
Home | The Team | Project Overview | Project Management | Project Documentation | Team Resources | Team Reflection |
---|
UI/UX Design | System Design | Testing | Administrative |
---|
Persona
Primary Persona
Secondary Persona
User Testing 1
Date: 20 Dec 2013
Location: LittleLives
Participant Group: LittleLives Staff
Participant Size: 8
Testing Documentations
Goals&Tasks&Data | Scripts | Instructions | Observation Forms | Questionnaires |
---|---|---|---|---|
Download | Download | Download | Download | Link |
Testing In Actions
Testing Results
Quantitative Data - Time taken to finish the task |
---|
Quantitative Data - No. of clicks to finish the task |
---|
Qualitative Data - Usability Rating |
---|
Frequently Seen Comments | Potential Problems & Improvements |
---|---|
"I could not find where to view my score" | The score display is not available and the score board design is not properly aligned. |
"The success messages are not obvious enough for the users" | Change the font size or color of success messages. |
"Accept and Reject buttons are not readable" | Change the font size and color of the buttons |
"The rules for knowledge are not easy and hard to remember" | Will implement 'Help' in later sprint when major functions are done |
"The navigation bar in Knowledge Challenge takes up too many spaces and is not professional" | Change to hidden navigation bar at bottom |
"There are too many unnecessary information in Scoreboard, which makes the overall design very crowded" | Limited the information displayed in Scoreboard and shift it to the left of the screen |
"I cannot view my status of challenges that I answered previously" | Create a new page, which displays "Challenge Status" |
User Testing 2
Date: 18 Jan 2014
Location: The Learning Lab (United Square)
Participant Group: Secondary Grade 2 - 4 Students
Participant Size: 12;
Testing Documentations
Goals&Tasks&Data | Scripts | Instructions - Set 1 | Instructions - Set 2 | Observation Forms |
---|---|---|---|---|
Download | Download | Download | Download | Download |
Testing In Actions
Testing Results
Quantitative Results
Qualitative Results
Top Comments | Potential Problems & Improvements |
---|---|
"The 3 horizontal lines don’t really clearly inform me of its purpose" | Remove the horizontal lines and standardize the menu format |
"There should be some instructions on choosing the questions for the knowledge challenge" | Add in step-by-step guides for users when sending the challenge |
"The landing page of Knowledge challenge is too blank and confusing for the first time user" | Change the layout of the landing page of knowledge challenge. |
"Very hard to find where to search friend" | Standardize the top tool bar and merge the search function in. |
Generally the system is hard to use for the first time user. Quite a few unnecessary pages and icons. | UI Revamp seems necessary, but need to further discuss with client and supervisor |
Comparing with UT1
User Testing 3
Date: 15 Feb 2014
Location: The Learning Lab (United Square)
Participant Group: Primary 5 - 6 Students
Participant Size: 12;
Testing Method: A/B Testing. This to...
- See the user preference on the side/top tool bar
- Test the difference between these two options statistically.
2 systems are identical except for...
- System A has only the side tool bar. Refer to here.
- System B has only the top tool bar. Refer to here.
Testing Documentations
Goals&Tasks&Data | Scripts | Instructions | Observation Forms |
---|---|---|---|
Download | Download | Download | Download |
Testing in Actions
Testing Results
Quantitative Results
T-test Analysis
Since two different groups of participants test our System A and System B, therefore we ran the statistical standard T-Test for between subjects.
- Test: Two-tailed t-test at 95% significance level (α=5%)
- Independent Variable: System A vs. System B
- Dependent Variable: Mean time taken to complete the Ask Question task
- Let μ0 be the mean time to complete the task using System A(control).
- Let μ1 be the mean time to complete the task using System B(treatment).
- Hypotheses:
- Null Hypothesis h0: μ0≠μ1
- Alternative Hypothesis: h1: μ0=μ1
- P-value:
- As calculated using Excel formula: T.Test(array1,array2,2,3), p≈0.02=2%
- p < α, then significant, not by chance.
- Therefore we do not reject H0.
- Conclusion: H0 is true and thus the mean time taken in completing the tasks is significantly different, not by chance.
Comparing with UT2
Internal Testing
Sprint | Test Cases |
---|---|
Sprint 1 | Download |
Sprint 2 | Download |
Sprint 3 | Download |
Sprint 4 | Download |
Sprint 5 | Download |
Sprint 6 | Download |
Sprint 7 | Download |
Sprint 8 | Download |