NattyTestCases

Unity/launcher

User runs Launcher for the first time

Name: User runs Launcher for the first time

Case ID: unilau-001
Depends on: User has not yet added entries to or removed entries from Launcher

  • Steps

    1. Launcher displays entries for: a Browser (e.g. Firefox, Chrome), an email application (e.g. Evolution Mail, Yahoo! Mail), a chat applicaiton (e.g. Empathy Instant Messenger), a music jukebox application (e.g. Rhythmbox, Spotify), a photos application (e.g. F-Spot), a web cam photobooth application (e.g. Cheese), a note-taking application (e.g. Tomboy Notes), (GNOME) Control Center, Ubuntu Software Center, Workspaces, Applications (Place), Files (Place), and Trash.
      USE CASE ENDS
      1.b Variation: User previously placed application launchers in GNOME Panel/AWN/Docky

      • 1 Launcher inspects the settings belonging to these other applications to approximate the entries the user will place in the Launcher.

      • 2 Launcher gleans ordered lists of Launcher entries from each source.

      • 3 Launcher de-duplicates and carefully merges entries into a single list, preserving the entry ordering exhibited by each source.

      • 4 Launcher uses this list of entries as the default configuration.
        RETURN TO 8

      1.c Variation: Computer does not have a web cam

      • 1 The webcam photobooth application is omitted from the Launcher.

    Verification

    • The Launcher entry's label is displayed


Placing the cursor over a Launcher entry

Name: Placing the cursor over a Launcher entry

Case ID: unilau-002
Depends on: None

  • Steps

    1. User places the cursor over a Launcher entry.

    2. Entry displays its name label.

    3. User moves the cursor off of the Launcher entry.

    4. Entry hides its name label.

    Verification

    • The Launcher entry's label is displayed


Activating a Launcher entry with the cursor

Name: Activating a Launcher entry with the cursor

Case ID: unilau-003
Depends on: The Launcher contains at least one entry

  • Steps

    1. User places the cursor over the Entry.

    2. User clicks the Entry. Double-click protection makes double-click act as single-click.

    3. Launcher makes Entry the focused entry.

    4. Entry hides its name label, and keeps this label hidden until User replaces the cursor over the Entry.

    5. Application raises its windows above other application windows.
      USE CASE ENDS
      1.b Variation: There are more entries than can fit on the screen

      • 1 User places cursor over the Launcher.

      • 2 To bring the desired entry into view, User scrolls using any of the appropriate techniques described in the Interaction Overview, including edge-scrolling. See Dragging and Scrolling sections of the Interaction Overview for more details.
        video:https://chinstrap.canonical.com/~michaelforrest/launcher_panning.mov<<BR>> RETURN TO 1

      3.b Variation: The entry represents an application that is not running

      • 1 The corresponding application is launched and immediately focused.
        RETURN TO 4

      Notes

    Verification

    • The application corresponding to the entry clicked is running and focused


An entry becomes focused

Name: An entry becomes focused

Case ID: unilau-004
Depends on: The Launcher contains at least one entry

  • Steps

    1. Entry becomes focused; previously focused entry loses focus.

    2. All unminimized windows belonging to the corresponding application are raised above other application windows, preserving their existing positions and layering.

    Verification

    • The application corresponding to the entry clicked is running and focused


A window raises an alert

Name: A window raises an alert

Case ID: unilau-005
Depends on: None

  • Steps

    1. The entry corresponding to the application that owns the window exhibits alert visuals. See Icon notification for visual details.

    2. When the alert is dismissed, the entry should not longer exhibit the alert visuals.

    Verification

    • Alert visuals are exhibited by the corresponding Launcher entry until the alert is dismissed


User scrolls the Launcher

Name: User scrolls the Launcher

Case ID: unilau-006
Depends on: None

  • Steps

    1. User moves the cursor to the bottom edge of the Launcher. (This use case also applies to scrolling against the top edge of the Launcher). See Launcher scrolling for implementation details.

    2. Launcher auto-scrolls.

    3. User moves the cursor away from the edge of the Launcher.

    4. Launcher stops scrolling down.
      USE CASE ENDS
      3.a Variation: Launcher cannot scroll any further

      • 1 Launcher cannot scroll any further because there are no further entries to bring on-screen.

    Verification

    • Launcher scrolls vertically


Cycling between the focused and penultimately focused applications

Name: Cycling between the focused and penultimately focused applications

Case ID: unilau-007
Depends on: The Launcher contains at least two entries for running applications: the focused application, and at least one other running application

  • Steps

    1. The User presses the application switching keyboard shortcut.

    2. The penultimately focused running application becomes the focused application. The transition between applications is a straight cut, no overt animation is used.
      USE CASE ENDS
      1.b Variation: The focused application is the only running application

      • 1 In this case, the application switching keyboard shortcut has no effect.

    Verification

    • The entry corresponding to the penultimately focused running application becomes the focused entry


Cycling through running applications

Name: Cycling through running applications

Case ID: unilau-008
Depends on: The Launcher contains at least two entries for running applications.

  • Steps

    1. User presses Super↓Tab↓↑.

    2. Launcher enters switcher mode, displaying the entries of running applications in reverse chronological order by when they were last focused.

    3. Launcher indicates the penultimately focused running application.

    4. User presses Tab↓↑ (while continuing to hold Super) to move the indication down until the desired entry is indicated.

    5. User releases Super↑.

    6. Launcher exits switcher mode, displaying both Running and Normal entries in their original order.

    7. Launcher focuses to the entry selected in switcher mode.
      USE CASE ENDS
      1.b Variation: There is only one running application

      • 1 User presses Super↓Tab↓↑. (This is not a true variation, only an explicit mention that the Primary Scenario still obtains when there is only one running application; the Launcher enters switcher mode until Super↑ is released.)
        RETURN TO 2

      4.b Variation: There are more running entries than can fit on the screen

      • 1 User presses Tab↓↑ until the indication has moved at half-way down the screen.

      • 2 User presses Tab↓↑.

      • 3 Launcher scrolls up one position to put the next entry under the indication (rather than continuing to move the indication down).

      • 4 User continues to press Tab↓↑, causing the Launcher to scroll up one position until...

      • 5 Launcher scrolls up enough that the final running entry is brought on screen.

      • 6 User presses Tab↓↑.

      • 7 Launcher reverts to moving the indication down.
        RETURN TO 5

      4.c Variation: User causes the indication to move past the final running entry

      • 1 User causes the indication to move past the final running entry.

      • 2 Launcher scrolls to basis position if necessary.

      • 3 Launcher moves indication back to the first entry (corresponds to the Focused entry immediately before switcher mode was invoked).

    Verification

    • Another running application becomes the focused entry


Activating an entry using a keyboard shortcut

Name: Activating an entry using a keyboard shortcut

Case ID: unilau-009
Depends on: The Launcher contains an entry that is not currently focused

  • Steps

    1. The User presses Super↓N↓↑↑, where N is a single digit corresponding to an entry in the Nth position of the Launcher. For example, the User presses Super↓1↓↑↑ to focus the first entry in the Launcher, Super↓2↓↑↑ for the second entry, etc. Super↓0↓↑↑ corresponds to the tenth entry.

    2. The corresponding entry becomes focused.

    3. The corresponding application is focused.
      USE CASE ENDS
      1.b Variation: The User uses a digit that is out of range

      • 1 When the digit (N) used in the keyboard shortcut is a number greater than the number of entries, the shortcut has no effect.
        USE CASE ENDS

      3.b Variation: The corresponding application is not running

      • 1 The corresponding application is launched.

      • 2 The corresponding application is focused.

    Verification

    • The entry in the position corresponding to the digit used in the keyboard shortcut is focused.


Displaying Launcher entry position overlays for use in keyboard shortcuts

Name: Displaying Launcher entry position overlays for use in keyboard shortcuts

Case ID: unilau-010
Depends on: None

  • Steps

    1. The User holds Super↓ for more than 300ms.

    2. The tiles with super key assigned unfold just enough to show the labels entirely over them.

    3. The digits 1-9 are displayed as overlays on the first nine Launcher entries; 0 is displayed on the tenth Launcher entry;

    4. Additional shortcuts are displayed on other Places which may be in the Launcher:<<BR>> "A" is displayed on the Applications Place.
      "F" is displayed on the Files Place.
      "W" is displayed on the Workspaces Place.
      "T" is displayed on the Deleted Items.

    5. Releasing Super↑ causes the entry overlays to fade out immediately and the Launcher to return to its original position (folding if necessary).

    Verification

    • The Launcher displays entry position overlays for use in keyboard shortcuts


Adding an entry by dragging an item from Applications place

Name: Adding an entry by dragging an item from Applications place

Case ID: unilau-011
Depends on: None

  • Steps

    1. The User drags an Application item from the Applications place into the drag safe zone.

    2. The Launcher unfolds based on the vertical position of the cursor.

    3. A line is drawn between the closest two entries to the cursor position to indicate where the entry will be placed.

    4. The drag continues over the Launcher.

    5. All icons whose centers fall below the cursor position on the vertical axis slide down one position to make room for the icon being dragged. If the item is dragged below the bottommost application entry, an empty position is drawn before Places.

    6. While the user is still moving the cursor to position the icon, resident icons should continue to slide upward or downward to leave an empty position near the cursor.

    7. Once the user decides where to place the icon, the user drops the icon over the Launcher and the empty position revealed by the resident icons is occupied by the icon dropped.
      USE CASE ENDS
      3.a Variation: The item dragged cannot be added

      • 1 When the item being dragged cannot be added--for example, if it is a not an Application item but rather a reference to an application available in the Software Center--no line is drawn between entries and the resident entries should not slide to create an empty slot.

      • 2 The user will get the impression that the item cannot be placed in the Launcher, as no empty position is available, so the user will discontinue the drag.
        USE CASE ENDS

      4.b Variation: The user drags the icon out of the drag safe zone without dropping it

      • 1 When the cursor is moved out of the drag safe zone, the Launcher returns to its normal state; any icons that have moved out of place to make room for the new icon return to their starting positions.

      • 2 At this point, the user may discontinue the drag by dropping the item, or may drag the item back into the drag safe zone to reopen the empty position.
        USE CASE ENDS

      7.a Variation: The item dragged is already present in the Launcher

      • 1 The icon moved slides from its old position to its new position. This move should be animated so the user understands what has happened, rather than believing that the Launcher has spontaneously changed icon order.

      • 2 Icons below the old position slide upward one position.

    Verification

    • An entry is added to the Launcher where the item is dropped


Removing an entry from the Launcher

Name: Removing an entry from the Launcher

Case ID: unilau-012
Depends on: The Launcher contains at least one entry

  • Steps

    1. The User right-clicks on an entry to display the QuickList for that entry.

    2. The User chooses the QuickList menu entry labeled "Remove from Launcher".

    3. The removed entry disappears from the Launcher.

    4. Any entries below the empty Launcher position slide upward to fill the empty position.
      USE CASE ENDS
      1.a Variation: The User drags the entry off the Launcher

      • 1 The User drags the entry horizontally to the right to release it from the Launcher.

      • 2 The Launcher now behaves exactly as when dragging an application to add it to the Launcher (2.11).

      • 3 If the drag leaves the drag safe zone, a minus symbol is affixed to the cursor.

      • 4 The User drops the entry, causing the dragged representation of the entry to disappear.
        RETURN TO 4

      1.b Variation: Entry is removed by the system (rather than by the User)

      • 1 When an application corresponding to an unpinned entry is removed (e.g. using apt, synaptic, Software Center, etc.), its entry quietly fades from the Launcher.
        RETURN TO 4

      2.a Variation: The corresponding application is still running

      • 1 The "Remove from Launcher" menu entry is instead a checkbox menu entry labeled "Keep in Launcher" in a checked state.

      • 2 The User clicks the menu entry to remove the check.

    Verification

    • The entry is removed from the Launcher


Adding an unpinned entry

Name: Adding an unpinned entry

Case ID: unilau-013
Depends on: GVim is not running

  • Steps

    1. Places move down one position to create an empty position for the GVim entry to be placed in.

    2. An entry for GVim appears is added in the empty position.

    3. The GVim entry receives focus.
      USE CASE ENDS
      1.b Variation: Adding GVim makes it so there are more entries than can fit on the screen

      • 1 The Launcher fold until an empty position is visible at the tail of the Launcher.

    Verification

    • The entry for GVim is focused (and present) in the Launcher


Pinning an unpinned entry

Name: Pinning an unpinned entry

Case ID: unilau-014
Depends on: An unpinned entry is present in the Launcher

  • Steps

    1. The User right-clicks on the Launcher to reveal its QuickList.

    2. The User clicks the "Keep in Launcher" QuickList menu entry so it becomes checked.

    Verification

    • The unpinned entry becomes pinned (stays in the Launcher when not running)


Dragging and dropping a selection onto an entry

Name: Dragging and dropping a selection onto an entry

Case ID: unilau-015
Depends on: None

  • Steps

    1. User begins dragging a selection (e.g. files, text).

    2. User holds the drag over the desired entry in the Launcher for a short delay.

    3. Windows belonging to the corresponding application spread and the entry shows its DropList.

    4. The primary entry is displayed in the Drag-over state.

    5. The User drops the selection over the Launcher entry.

    6. The DropList's primary entry is activated.

    7. The DropList closes and windows return to their previous (unspread) positions.
      USE CASE ENDS
      2.a Variation: The desired entry is not on the screen

      • 1 The User drags while edge-scrolling to scroll the desired entry into view. DropLists are not shown and windows are not spread while the Launcher is being scrolled.
        RETURN TO 2

      2.b Variation: The selection is dropped before it is held over the entry for a short delay

      • 1 The selection is dropped before it is held over the entry for a short delay.

      • 2 The DropList's primary entry is activated.
        USE CASE ENDS

      4.a Variation: The DropList's primary entry cannot accept the drop

      • 1 The DropList's primary entry is in the Inactive state.

      • 2 The User drops the selection over the Launcher entry.

      • 3 No DropList entry is activated (no drop action is performed).

      • 4 The DropList closes and windows return to their previous (unspread) positions.
        USE CASE ENDS

      5.a Variation: The drop occurs in negative space

      • 1 Dropping in negative space (i.e. the space not occupied by individual spread windows, the DropList, the Launcher, or the Places Bar) discontinues the drag (i.e. hides the DropList, unspreads windows).

    Verification

    • The file dropped is opened in the corresponding application


Dragging and dropping a selection onto a DropList entry

Name: Dragging and dropping a selection onto a DropList entry

Case ID: unilau-016
Depends on: None

  • Steps

    1. The User drags a selection (e.g. files, text) over an entry in the Launcher.

    2. Windows belonging to the corresponding application spread and the entry shows its DropList.

    3. The User drags the selection over the desired DropList entry.

    4. The DropList entry becomes Selected to indicate that the drop will be valid if performed.

    5. The User drops the selection over the desired DropList entry.

    6. The action corresponding to the DropList entry receiving the drop is activated.

    7. Application windows unspread and the DropList disappears.
      USE CASE ENDS
      3.a Variation: The User drops the selection in negative space

      • 1 The User drags the selection over negative space (space not occupied by spread windows, the DropList, the Launcher, or the Places Bar).

      • 2 The User drops the selection, ending the drag operation.
        RETURN TO 7

      4.a Variation: The DropList entry cannot accept the drop

      • 1 The DropList entry is in an Invalid state, as the drop will be invalid and have no effect if performed.

      • 2 The User discontinues the drag by dropping in negative space.

    Verification

    • The action represented by the DropList entry is performed on the selection


Dragging and dropping a selection onto a specific window

Name: Dragging and dropping a selection onto a specific window

Case ID: unilau-017
Depends on: The Launcher contains a running entry with open windows

  • Steps

    1. The User drags the selection over an entry in the Launcher.

    2. After a short delay, the entry's DropList is displayed and the windows belonging to the corresponding application are spread.

    3. The User drags the file over the desired target window and holds it there for a long delay. After a long delay, the target window and its parent application become focused.
      USE CASE ENDS
      2.a Variation: The application has no open windows

      • 1 Only the DropList is shown.
        USE CASE ENDS

      2.b Variation: The drop occurs in negative space

      1. Dropping in negative space (i.e. the space not occupied by individual spread windows, the DropList, the Launcher, or the Places Bar) discontinues the drag (i.e. hides the DropList, unspreads windows).
        USE CASE ENDS

      3.a Variation: Some windows are minimized

      • 1 Minimized windows should appear as normal windows when all application windows are spread. This may require minimized windows to become temporarily unminimized, and then re-minimized appropriately.
        RETURN TO 4

      3.b Variation: The file is dragged over another entry

      • 1 Once an application's windows have been spread out, dragging the file over another running application and holding it there for more than a short delay shows the DropList and spread windows for that entry.

    Verification

    • The target window is raised, and the application to which the window belongs is focused


User switches to a specific window

Name: User switches to a specific window

Case ID: unilau-018
Depends on: The Launcher contains a running entry with open windows

  • Steps

    1. User double-clicks on an Entry, or single-clicks the focused Entry.

    2. Windows belonging to the corresponding application are spread out.

    3. User clicks on the desired window.

    4. Windows return to their previous positions and stack-order, but they are now above all other windows, and the clicked window is the active window.

    5. Application corresponding to the clicked window is focused.
      USE CASE ENDS
      2.a Variation: The corresponding application has no open windows

      • 1 No windows are spread, because none are available.
        USE CASE ENDS

      2.b Variation: The corresponding application is not running

      • 1 The application is launched.
        USE CASE ENDS

      3.a Variation: User clicks in negative space or presses Escape

      • 1 User clicks in negative space or presses Escape.

      • 2 Windows return to their previous positions.

      • 3 The application that was previously focused remains focused.

    Verification

    • The User chooses the desired window, causing it to become the active window, and the parent application and corresponding entry become focused as well


Moving an entry to a different position

Name: Moving an entry to a different position

Case ID: unilau-019
Depends on: The Launcher contains more than one entry

  • Steps

    1. The User places the cursor over the entry she wishes to relocate.

    2. The User drags the entry off the Launcher to the right, into the drag safe zone.

    3. The entry's former position in the Launcher is closed.

    4. Dragging the entry upward causes entries above the empty position move downward to fill the empty position and vacate the position closest to the cursor. Entries move similarly (but in the opposite direction) if the User drags the entry below the empty position. (The behavior is exactly the same as if the user were adding a new entry by dragging an item from the Applications place.)

    5. The User drops the entry over the Launcher once the desired new position is empty.

    6. The entry is placed in the new position and becomes pinned if it is not pinned already.
      USE CASE ENDS
      Notes

    Verification

    • The entry is relocated to where it is dragged


Quitting an application via QuickList

Name: Quitting an application via QuickList

Case ID: unilau-020
Depends on: The Launcher contains a running entry

  • Steps

    1. The User right-clicks on the entry to reveal its QuickList.

    2. The User clicks the menu entry labeled "Quit".

    3. The application quits with appropriate care (e.g. displays a save confirmation dialog if necessary).

    4. If the entry is pinned, its visual treatment changes to indicate that it is not running.

    5. The previously focused application becomes focused, and its Launcher entry becomes focused.
      USE CASE ENDS
      4.b Variation: The quited entry is not pinned

      • 1 The entry is removed from the Launcher.

      • 2 All entries below the entry removed slide upward to close the empty position.
        RETURN TO 5

      5.b Variation: The quited application was not the active application

      • 1 Focus never changes; the originally active application remains active.
        USE CASE ENDS

      5.c Variation: No other applications are running

      • 1 When no other applications are running, the Home screen is shown in the Dash.

    Verification

    • The application quits.


Adding a Prism entry

Name: Adding a Prism entry

Case ID: unilau-021
Depends on: The Launcher contains more than one entry

  • Steps

    1. The User drags a Firefox Bookmark from within Firefox.

    2. User drags the bookmark over the Launcher. The Launcher behaves exactly as if the User were dragging a new application item to the Launcher.

    3. The User drops the bookmark on the Launcher to add a new entry.

    4. A new entry representing a Prism instance for the dropped Firefox Bookmark appears in the Launcher.
      USE CASE ENDS
      1.b Variation: The User drags a selected URL

      • 1 User selects text containing just a URL from any source.

      • 2 User drags the selected text over the Launcher. The Launcher behaves exactly as if the User were dragging a new application item to the Launcher.

    Verification

    • A new entry representing a Prism instance for the dropped web resource appears in the Launcher.


User clicks on a Place Entry

Name: User clicks on a Place Entry

Case ID: unilau-022
Depends on: None

  • Steps

    1. User clicks the a Place entry (here, the Applications Place entry is clicked).

    2. Dash opens and displays the appropriate place, and the corresponding Launcher entry enters Focused state.
      USE CASE ENDS
      1.a Variation: User activates the QuickList for the Place Entry

      • 1 User activates the QuickList for the Place Entry. "Remove from Launcher" is present but insensitive.

      • 2 User clicks a Place section title (e.g. "Office"). These section titles correspond to the sections in the Place (same sections, same order).

      • 3 Dash opens and displays the clicked section in the appropriate place.

    Verification

    • User opens Applications Place in the Dash


User switches workspaces

Name: User switches workspaces

Case ID: unilau-023
Depends on: None

  • Steps

    1. User clicks the Workspaces Entry.

    2. Workspaces are displayed in an overlay.

    3. User clicks the desired Workspace.

    4. Clicked Workspace becomes active.
      USE CASE ENDS
      1.a Variation - User activates the QuickList for the Workspaces entry

      • 1 User activates the QuickList for the Workspaces Entry.
        USE CASE ENDS

      1.b Variation: User drags a window to a workspace

      • 1 User drags a window over the Workspaces Entry for a short delay.

      • 2 Workspaces are displayed in an overlay.

      • 3 User drops the window on the desired workspace.

      • 4 The window is moved to the desired workspace.
        RETURN TO 3

      3.b Variation: User drags an individual window between workspaces

      • 1 User drags an individual window from one workspace and drops it in another.

      • 2 The window is moved to the desired workspace.

    Verification

    • User reaches the desired workspace


JeanBaptisteLallement/SandBox/NattyTestCases (last edited 2010-11-10 22:25:16 by ACaen-151-1-76-110)