Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Section
Column
width65%

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 or later)

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 all screens: Absence of horizontal scroll

Procedure:

  1. Drag the screen left and right while holding the device in portrait mode.

Expected results:

  • The screen should not shift left or right (i.e., it is fixed).
Test 1: Main exhibition page load

Procedure:

  1. From the application home screen, tap invoke "Exhibitions" or its icon.
  2. At the Exhibitions page, tap on invoke "Simply Montreal" exhibition.
    (For VO: After the page load announcement, have VO read the screen from top to bottom. Also tap around the screen to check position of elements.)

Expected results:

  • (For VO: User should hear "Web page loaded - Exhibition".)
  • A back button, a home button, and the name of the exhibition should appear in the navigation bar, in that order. No other elements should be present on the bar.
  • At the top of the page, a brief information about the exhibition should appear. This information should include:
    1. The name of the exhibition (in a bigger text size),.
    2. A brief introduction,.
    3. Opening and closing dates (or the literal "Permanent exhibition").
    4. A "Read more" option.
  • Then information about the Catalogue should appear. This should include:
    1. The title "Catalogue" followed by the number of objects artifacts in the catalogue,.
    2. Some objectsartifacts, each with its thumbnail (as a link) and its name below. There should be a maximum of 4 objects artifacts per row.
      (For VO: The thumbnail links to artifacts should have a label indicating the name of the artifact they are linked to.)
    3. A "View the full catalogue" option.
    Then information about the Guestbook should appear. This should include:
    1. The title "Guestbook" followed by the number of current comments,
    2. An "Add a note" option,
    3. The most recent comment,or the text "Be the first to post a note" (if there are not comments yet). In case there's a comment, it should contain:
      1. its author's name,
      2. his/her location,
      3. comment date,
      4. the comment itself,
      5. "Report abuse" option.
    4. A "link.
    5. A Guest book with number of comments in brackets followed by and "Add Note" option, the comments, and a "Read all comments" option.
Test 2: Read more information about the exhibition (cont'd from Test 1)

Procedure:

  1. Complete Test 1.
  2. Tap on Invoke "Read more" option.
  3. (For VO: After the page load announcement, have VO read the screen from top to bottom. Also tap around the screen to check position of elements.)

Expected results:

  • (For VO: User should hear "Web page loaded - About".)
  • A back button, a home button, and the name of the exhibition should appear in the navigation bar, in that order. No other elements should be present on the bar.
  • General contents about the exhibition should appear in the page (to be checked in another test).
Test 3: View the full catalogue (cont'd from Test 1)

Procedure:

  1. Load the main exhibition pageComplete Test 1.
  2. Tap on Invoke "View the full catalogue".
  3. (For VO: After the page load announcement, have VO read the screen from top to bottom. Also tap around the screen to check position of elements.)

Expected results:

Test 5
  • (For VO: User should hear "Web page loaded - Catalogue".)
  • A back button, a home button, the name of the exhibition and a button to switch to list view should appear in the navigation bar, in that order. No other elements should be present on the bar.
  • The exhibition objects artifacts should appear in grid view (to be in-depth checked in another test).
Test 4: View the whole Guestbook

Procedure:

  1. Load the main exhibition page.
  2. Tap on "Read all comments".

Expected results:

  • A back button, a home button, and the name of the exhibition should appear in the navigation bar, in that order. No other elements should be present on the bar.
  • An option to add a note and the list of current comments should appear (to be checked in another test).
  • (For VO: User should hear the link labels for each item in the grid.)
Test 4: View an object's information (cont'd from Test 1)

Procedure:

  1. Load the main exhibition pageComplete Test 1.
  2. Tap directly on Invoke an object artifact in the Catalogue section directly. 

Expected results:

  • A back button, a home button, and the name of the object should appear in the navigation bar, in that order. No other elements should be present on the bar.
  • Information about the selected object should appear on the page (to be in-depth checked in another test).
Test 6: Report abuse on a guestbook comment

**Should we specify with/without being signed?

Procedure:

  1. Load the main exhibition page.
  2. Tap on "Report abuse" option, in the Guestbook section.

Expected results:

  • The "Report abuse" option should be replaced by the static text "Abuse reported. Pending moderator review."
Test 7: Add a note to the guestbook

**Should we specify with/without being signed?

Procedure:

  1. Load the main exhibition page.
  2. Tap on "Add a note" option, in the Guestbook section.

Expected results:

A back button, and the title "Comment entry"
  1. (For VO: After the page load announcement, have VO read the screen from top to bottom. Also tap around the screen to check position of elements.)

Expected results:

  • (For VO: User should hear "Web page loaded - Artifact".)
  • A back button, a home button, and the name of the artifact should appear in the navigation bar, in that order. No other elements should be present on the bar.
  • The screen should contain:
    1. An empty text entry field
    2. "Cancel" and "Submit" buttons
    3. An on-screen keyboard.
Test 8: Submit a note to the guestbook (cont'd from Test 7)

Procedure:

  1. Complete Test 7.
  2. Write a sentence in the text entry field.
  3. Tap on "Submit".

Expected results:

  • In the exhibition's main page, the comment at the Guestbook section should appear updated with the submitted comment.
  • The "Report abuse" option should be replaced by a "Delete" option.
  • The rest of the page should remain as before.
Test 9: Delete one's own note (cont'd from Test 8)

Procedure:

  1. Complete Test 8.
  2. Tap on "Delete" option below the recently submitted note.

Expected results:

  • In the exhibition's main page, the comment should be removed with a slide shutting animation.
  • No confirmation dialogue should appear.
  • The guestbook section displays the previous note (the most recent before the deleted one).
  • Information about the selected artifact should appear on the screen.
  • There should be two buttons (Collect and Comment) at the top left of the screen

Boundary Tests

Description: Ensures proper functionality at the input limits.

Protocol: Perform these tasks on the following site.

Column
width35%
tocindent

An exhibition wireframes
An exhibition storycards

Panel
borderColor#321137
bgColor#fff
titleBGColor#c1b7c3
titleOn this page
borderStylesolid
title
Specifications
8px
stylenone
solid
Panel
borderStyle
borderColor#321137
bgColor#fff
titleBGColor#c1b7c3
borderStylesolid
titleSpecificationsOn this page
Table of Contents
indent

Code entry wireframes
Code entry storycards

10px
stylenone