Difference between revisions of "IS480 Team wiki: 2013T2 Invenio Usability Test"
Line 131: | Line 131: | ||
===Test Results=== | ===Test Results=== | ||
+ | {| style="border: 1px solid darkgray; text-align: center;font-siz:14px; height:50px" | ||
+ | |scope="row" width="1000" style="text-align: left; background: #eeeeee"| | ||
+ | <b>What do you like about the application?</b> | ||
+ | *Easy to add a maintenance schedule | ||
+ | *Makes life easier | ||
+ | *Simple interface | ||
+ | *Easy to log in | ||
+ | *Functional and something new for the industry | ||
+ | *Main page very clear | ||
+ | <br> | ||
+ | <b>What do you dislike about the application?</b> | ||
+ | *Device pop up registry success, but tag is invalid | ||
+ | *Web console login trouble when user is already logged in Android app | ||
+ | *Long information keyed into registration process | ||
+ | *Too many histories stored in phone | ||
+ | <br/> | ||
+ | |||
+ | <b>What are some of the issues you faced while performing the tasks?</b> | ||
+ | *Server unstable | ||
+ | *Had to wait for server to start | ||
+ | *Cannot use web console when Android app is logged into same account | ||
+ | <br/> | ||
+ | |||
+ | <b>How can we improve this application to give you a better / user experience?</b> | ||
+ | *Make the display clearer | ||
+ | *Login screen should show soft keyboard automatically | ||
+ | *Upload personal photo | ||
+ | *Allow user to key in tag ID if cannot read tag | ||
+ | *Read tag > remarks should display "" instead of null | ||
+ | *Make the UI nicer | ||
+ | |} | ||
===Documentation=== | ===Documentation=== |
Revision as of 13:59, 6 February 2014
Home | Our Team | Project Overview | Project Management | Project Documentation | Learning Outcomes |
Use Cases | Diagrams | Usability Test | Minutes |
Contents
Internal Testing
Our team has conducted internal testing using regression testing at the end of each iteration.
Please refer to the following for our test plan and test cases:
Usability Test 1
Date & Venue
Date: 24 Jan 2014 |
Participants
No. of Participants: 6
|
Scope of Test
Testing Method
We have designed different scenarios in a series of tasks, for the participants to follow during User Test 1. They would be required to figure out how to complete the set of tasks allocated to them. Facilitators would be beside them to observe and record the actions that the users have made in order to complete the tasks assigned. |
Test Results
What do you like about the system?
- Easy to add a maintenance schedule
- Makes life easier
Documentation
|
Usability Test 2
Date & Venue
Date: 7 February 2014 |
Participants
No. of Participants: 2
Scope of TestTesting Method
Test Results
Documentation
|