Labs/Ubiquity/Usability/Usability Testing: Difference between revisions
Indolering (talk | contribs) m (New page: == Severity Rankings == S1 = Annoyance S2 = Loss of data or deterrent to use S3 = Makes Ubiquity either inaccessible or broken.) |
Indolering (talk | contribs) |
||
| (19 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
== | Guidelines, resources, etc for Usability testing. | ||
== Classical Usability testing == | |||
Classical usability testing is sitting down participants and watching them use the software. This can be used to identify mismatches between the software model and the users mental model. | |||
[[Labs/Ubiquity/Usability/Usability_Testing/How To | How to series]] on classical Usability testing. | |||
[[Labs/Ubiquity/Usability/Usability_Testing/Sync | Scripts]] for syncing tagging data. | |||
[[Labs/Ubiquity/Usability/Usability Testing/#Usability Tests | Usability tests]] on Ubiquity | |||
== Using Test Pilot == | |||
Info on Test pilot + Ubiquity. | |||
== UI Triangulation == | |||
See main page [[Labs/Ubiquity/Usability/Usability_Testing/UI Triangulation | Usability Triangulation]] | |||
UI Triangulation ensures that different tracking mechanisms (bug tracker tickets, Get Satisfaction tickets, and results from usability testing) are cross referenced and prioritized like programming bugs. It uses UI Severity and frequency ratings to prioritize bugs similar similar to programming bugs. | |||
Severity + Frequency + human factoring = Priority | |||
== Templates == | |||
Not traditional MediaWiki templates, but a [[Labs/Ubiquity/Usability/Usability Testing/Session Template | good starting point]] for someone to c/p. | |||
== Usability Tests == | |||
* [[Labs/Ubiquity/Usability/Usability Testing/Fall 08 1.2 Tests | Fall 08 1.2 Tests]] (exploratory testing) | |||
* [[Labs/Ubiquity/Usability/Usability Testing/Spring 09 1.8 Tests | Spring 09 Tests]] (A/B documentation testing and effectiveness of priming using advertising) | |||
== See also == | |||
[[Labs/Ubiquity/Usability/Usability_Testing/How_To | How To Guide]] | |||
[[Category:Usability|Usability]] | |||
[[Category:Usability Tests|Usability Tests]] | |||
[[Category:Ubiquity]] | |||
Latest revision as of 21:52, 13 June 2010
Guidelines, resources, etc for Usability testing.
Classical Usability testing
Classical usability testing is sitting down participants and watching them use the software. This can be used to identify mismatches between the software model and the users mental model.
How to series on classical Usability testing.
Scripts for syncing tagging data.
Usability tests on Ubiquity
Using Test Pilot
Info on Test pilot + Ubiquity.
UI Triangulation
See main page Usability Triangulation
UI Triangulation ensures that different tracking mechanisms (bug tracker tickets, Get Satisfaction tickets, and results from usability testing) are cross referenced and prioritized like programming bugs. It uses UI Severity and frequency ratings to prioritize bugs similar similar to programming bugs.
Severity + Frequency + human factoring = Priority
Templates
Not traditional MediaWiki templates, but a good starting point for someone to c/p.
Usability Tests
- Fall 08 1.2 Tests (exploratory testing)
- Spring 09 Tests (A/B documentation testing and effectiveness of priming using advertising)