Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

QA overview

Environments

  • iPhone OS 3.0 or higher on iPhone 3G or 3GS
  • iPhone OS 3.0 or higher on iPod touch 1G, 2G or 3G

For testing Fluid Engage with VoiceOver: 

  • iPhone OS 3.0 or higher on iPhone 3GS
  • iPhone OS 3.0 or higher on iPod Touch 32 GB or 64 GB (Fall 2009 release)

Protocol overview

General QA guidelines

  • Does the tool behave the way that you would expect?
  • Are you surprised by anything?
  • Does something take longer than you would expect?
  • When the tool does something unexpected or takes too long to do something, does the tool provide appropriate feedback?

QA tests

Unit tests

Protocol: Launch the following websites to execute unit tests.

url to be filled

Task-oriented functional tests

Description: Ensures that the component is able to handle expected input.

Protocol: Perform these tasks after completing initial Engage setup (to be added: instructions on adding app to home screen).

Test 1: Visual feedback for options at the home page

Procedure:

  1. Load the application and tap on any language at the language selection screen.
  2. Once at the home page, tap on "Exhibitions".

Expected results:

  • The option should highlight. The highlight should persist until the finger leaves the screen.
  • (FOr VO: User hears "Exhibitions icon - (visited) link - image".
Test 2: Visual feedback for list items

Procedure:

  1. From home, tap on Exhibitions.
  2. Once at the Exhibitions page, tap on an item on the list (eg. "Simply Montreal").
    (For VO: After hearing "Web page loaded - Browse", tap on an item on the list (eg "Simply Montreal". Then double tap)

Expected results:

  • The list item should highlight. The highlight should persist until the finger leaves the screen.

For VO:

  • Upon single tap on thumbnail link, user hears ""Simply Montreal: Glimpses of a Unique City - (visited) link - image".
  • Upon single tap on text link, user hears "Simply Montreal: Glimpses of a Unique City - (visited) link".
  • User must not hear the Exhibition duration as a separate link.
  • After double tap user hears "Web page loaded - Exhibition")
Test 3: Visual feedback for buttons (cont'd from Test 2)

Procedure:

  1. Complete Test 2.
  2. At an Exhibition page (eg. "Simply Montreal"), tap on "View the full catalogue" in the Catalogue section.
    (For VO: At an Exhibition page (eg. "Simply Montreal"), tap on the link "View the full catalogue". Then double tap.)

Expected results:

  • The tapped button should highlight. The highlight should persist until the finger leaves the screen.
    (For VO: Upon single tap, user hears "View the full catalogue - (visited) link". After double tap user hears "Web page loaded - Catalogue")
Test 4: Visual feedback for options in the navigation bar (cont'd from Test 3)

Procedure:

  1. Complete Test 3.
  2. Being at the full catalogue page, switch to grid view using the button in the navigation bar.
    (For VO: Being at the full catalogue page, tap on the toggle button in the navigation bar.

Expected results:

  • The button in the navigation bar should highlight. The highlight should persist until the finger leaves the screen.
Test 5: Visual feedback for grid items (cont'd from Test 4)

Procedure:

  1. Complete Test 4.
  2. Being at the full catalogue page (grid view), tap on an item in the grid.

Expected results:

  • The grid item should highlight. The highlight should persist until the finger leaves the screen.
Test 6: Navigation, going back

Procedure:

  1. Go to the application home screen.
  2. Go to any page at least one screen away.
  3. Tap the back button.

Expected results:

  1. Back button should appear on the top left corner on screens at least one level away from a home start.
  2. Tapping back should bring the user back to the previous screen.
Test 7: Navigation, going home

Procedure:

  1. Go to the application home screen.
  2. Go to any page at least two screens away.
  3. Tap the home button.

Expected results:

  1. Home button should appear on the top left corner, to the right of the back button on screens at least two levels away from a home start (exception: text-entry screens, such as e-mail address entry or comment entry)
  2. Tapping the home button should bring the user back to the application home screen.

Task-oriented functional tests for VoiceOver

Description: Ensures that the component is able to handle expected input.

Protocol: Perform these tasks after completing initial Engage setup (to be added: instructions on adding app to home screen).

Test 1 (VO): Aural feedback for options at the home page

Procedure:

  1. On the home page, tap on "Exhibitions icon".

Expected results:

  • User hears "Exhibitions icon - (visited) link - image".
Test 2 (VO): Aural feedback for list items (cont'd from Test 1)

Procedure:

  1. Complete Test 1.
  2. Double tap on "Exhibitions icon".
  3. After hearing "Web page loaded - Browse", tap on an item on the list (eg "Simply Montreal").

Expected results:

  • User hears "Simply Montreal: Glimpses of a Unique City - (visited) link" when tapped on text.
  • User hears ""Simply Montreal: Glimpses of a Unique City - (visited) link - image" when tapped on image thumbnail.
  • User does not hear the Exhibition duration as a separate link.
Test 3 (VO): Aural feedback for buttons (cont'd from Test 2)

Procedure:

  1. Complete Test 2.
  2. Double tap on the "Simply Montreal ..." link.
  3. After hearing "Web page loaded - Exhibition"  tap on "View the full catalogue" in the Catalogue section.

Expected results:

  • User hears "View the full catalogue - (visited) link".
Test 4 (VO): Aural feedback for options in the navigation bar (cont'd from Test 3)

Procedure:

  1. Complete Test 3.
  2. Being at the full catalogue page, tap on the toggle button in the navigation bar.

Expected results:

  • User hears "Switch to grid view".
Test 5 (VO): Aural feedback for grid items (cont'd from Test 4)

Procedure:

  1. Complete Test 4.
  2. Double tap on the toggle button.
  3. After the grid view loads*, tap on an item in the grid.

(*Unable to check feedback for page load completion as there is no toggle button currently).

Expected results:

  • User hears "Description of link - (visited) link - image".
Test 6 (VO): Expanding a panel

Procedure:

  1. Load the home page, tap on "Enter object code" and double tap.
  2. After hearing "Web page loaded - Code entry" read through the page.
  3. Tap a two-digit, valid object code (see object code list for possibilities).
  4. After the object page loads*, tap on "Show Audio and video" and double tap.

(*Unable to check feedback for object page load completion as this doesn't work currently).
Expected results:

*Unable to check VoiceOver behaviour.

Test 7 (VO): Contracting a panel (cont'd from Test 6)

Procedure:

  1. Complete Test 8.
  2. Tap on "Hide Audio and video"; then double tap.

Expected results:

*Unable to check VoiceOver behaviour.

Boundary Tests

Description: Ensures proper functionality at the input limits.

Protocol: Perform these tasks on the following site.

On this page
  • No labels