[UX] Baseline Horizon Usability Testing

Registered by Jaromir Coufal

We'd like to run some usability testing on the basic features that are available in Horizon currently today. The plan is to test 5-8 participants and have them run through tasks listed below. We will then analyze the data and bring any findings back to the community. The goal is that these findings will help drive improvements that can be made in the next release.

Blueprint information

Status:
Complete
Approver:
Jaromir Coufal
Priority:
Medium
Drafter:
Liz Blanchard
Direction:
Approved
Assignee:
Liz Blanchard
Definition:
Obsolete
Series goal:
None
Implementation:
Started
Milestone target:
milestone icon icehouse
Started by
Liz Blanchard
Completed by
Pieter

Related branches

Sprints

Whiteboard

Scenarios that participants will walk through:

Scenario: Launching an instance
Individual Tasks:
-Create a security key pair. (Could be set up optionally before test)
-Create a network. (Could be set up optionally before test)
-Import an image. (Could be optional)
-Launch an instance using security key pair X, network Y, and image Z. (Could add in additional requirements such as size or number of instances to launch.)
-Confirm that instance was launched successfully.

Scenario: Understand how many vCPUs are currently in use vs. how much quota is left.
Individual Tasks:
-Check out Overview Page to review current quota use/limit details.

Scenario: Take a snapshot of an Instance to save for later use.
Individual Tasks:
-Either Launch an instance successfully, or identify a running instance in the instance view.
-Choose to take a snapshot of that instance.
-Confirm that the snapshot was successful.

Scenario: Launch an instance from a snapshot.
Individual Tasks:
-Choose to either create an instance and boot from a snapshot, or identify a snapshot to create an instance from.
-Confirm that the instance was started successfully.

Scenario: Launch an instance that boots from a specific volume.
Individual Tasks:
-Create a volume (Could be set up optionally before test)
-Launch an instance using Volume X as a boot source.

[5-28-2014 lblanchard] Analysis organized the findings into a few different categories based on priority of fixing for end users...presented these at Summit to the Horizon community.

High Priority
*Improve error messages and error message catalog. - https://blueprints.launchpad.net/horizon/+spec/improve-error-message-details-for-usability
* Fix Launch Instance workflow for end user and power user. - https://blueprints.launchpad.net/horizon/+spec/launch-instance-ux-enhancement
* Improve informational help information about form fields, not just text input but everything
* Fix terminology. (e.g. launch instance, boot, shutoff, shutdown, etc.)
* Show details for key pair and network in Launch Instance workflow.
* Recommend a new Information Architecture.

Medium Priority
* Create UI guidelines (of best practices) for Developers to use.
* Improve Online Help.
* Provide clearer indication the application is working after clicking a button and the application doesn’t respond immediately.
* Ensure consistency of network selection. (Drag and drop of networks very inconsistent from the other pieces of the launch instance modal)
* Create consistency of visualizations and section of action button recommendations on Instance table.
* Suggest defaults for the forms entry fields.
* Provide Image information details during image selection.

Low Priority
* Allow users to edit the network an instance after launching instance.
* Resolve confusion around the split inline actions button.
* Explain what the Instance Boot Source field in Create Instance modal.
* Provide description/high level information about flavors for flavor selection.
* Make sorting clearer visually.
* Provide solution for subnet checkbox to improve usability.

Nice to Have
* Provide “Save as Draft” option in the wizard.
* Change security group default name to “Default security group”.

(?)

Work Items

Work items:
Put together screener to find participants: DONE
Send out screener to mailing lists, LinkedIn groups: DONE
Choose participants based on screener feedback: DONE
Test participants: DONE
Analyze Results: DONE
Deliver Findings to community: DONE
Create any blueprints or bugs needed to close out this blueprint: INPROGRESS

This blueprint contains Public information 
Everyone can see this information.