Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Fluid Engage code entry QA test plan

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?
Column
width35%
Panel
borderColor#321137
bgColor#fff
titleBGColor#c1b7c3
titleOn this page
borderStylesolid
Table of Contents
minLevel2
maxLevel5
indent10px
Panel
borderColor#321137
bgColor#fff
titleBGColor#c1b7c3
titleSpecification
borderStylesolid

Code entry wireframes
Code entry storycards

QA

...

tests

...

Report issues at: http://issues.fluidproject.org/secure/Dashboard.jspa

Note

Please search for issues before reporting them, so as to limit the number of duplicate entries.

Unit Tests

________________________________________________________

Wiki Markup
+Protocol{+}Launch the following websites to execute unit tests. \[\]

Task Oriented Functional 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

...

Wiki Markup
\[\] <span style="color: #ff0000">&#42;**Note this URL will change</span>

  • Expected results
    • One title should appear, centered at the top, taking up exactly one line. If the title would otherwise extend past one line, the excess should be truncated and replaced with ellipses (i.e., "...")
    • A list of 20-30 artifacts should show
    • For each artifact, if the artifact has an image, there should be a thumbnail image to the left. If the artifact has no image, a blank thumbnail saying "no image" should be present.
    • Each artifact should have a title line taking exactly one line. If the artifact has a title that would otherwise extend past one line, the excess should be truncated and replaced with ellipses (i.e., "..."). If the artifact has no title, it should read "no title"
    • Each artifact may or may not have a subtitle

Test 2: Swiping up and down

  • Procedure
    1. Swipe the screen up several times, until it reaches the bottom limit
    2. Swipe the screen down several times, until it reaches the upper limit
  • Expected results
    • When swiping up, the screen should move downwards
    • When swiping down, the screen should move upwards
    • No links should be activated

Test 3: Swiping left and right

  • Procedure
    1. Swipe the screen to the left
    2. Swipe the screen to the right
  • Expected results
    • Nothing should happen
    • No links should be activated

Test 4: Activating a link

  • Procedure
    1. Touch the following spaces within the bounding area of an artifact list item, navigating back to the specified URL after each: the thumbnail icon, the title/subtitle, empty white space.
  • Expected results
    • You should be taken to the artifact view corresponding to the artifact list item you touched.

Boundary Tests

________________________________________________________

DescriptionEnsures proper functionality at the input limits

...

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: Page load

Procedure:

...

  1. From the application home screen, invoke "Enter object code" or its icon.
  2. (For VO: After the screen 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 - Code entry".)
  • A back button and "Enter object code" title should appear in the navigation bar, in that order. No other elements should be present on the bar.
  • Short instructions (e.g., "Enter code from the object's label to learn more about the object") should appear below the navigation bar.
  • Empty fields should appear below the instructions (in the case of Engage 0.3, it should be two empty fields).
    (For VO: User should be able to tap on the two fields and hear them as being empty.)
  • A keypad should appear below the empty fields, which includes the numbers 0-9, and a delete key.
    (For VO: User should be able to tap on the number pad and hear the numbers and the delete key.)
Test 2: Enter a single-digit (cont'd from Test 1)

Procedure:

  1. Complete Test 1.
  2. Invoke a number from the keypad.

Expected results:

  • (For VO: User should hear which number was punched along with a message that it has been entered.)
  • The tapped number should appear in the left text field.
    (For VO: User should be able to tap on the field and hear the number.)
  • Nothing else should have changed.
Test 3: Delete a single-digit (cont'd from Test 2)

Procedure:

  1. Complete Test 2.
  2. Invoke the delete key.

Expected results:

  • The right-most number should disappear.
    (For VO: User should be able to tap on the field and hear it as being empty.)
  • Nothing else should have changed.
Test 4: Enter an invalid object code (cont'd from Test 1)

Procedure:

  1. Complete Test 1.
  2. Enter a two-digit, invalid object code (see object code list for possibilities).

Expected results:

  • An error should appear on the screen ("Invalid code. Please try again.", replacing the enter code instructions.
    (For VO: User should be able to hear the error message as soon as it appears on the screen.)
  • The number fields should clear after a brief moment (~0.5 seconds).
    (For VO: User should be able to tap on the two fields and hear them as being empty.)
  • The error message should persist.
    (For VO: User should be able to tap and listen to the error message.)
Test 5: Enter an invalid object code, again (cont'd from Test 4)

Procedure:

  1. Complete Test 4.
  2. Enter another two-digit, invalid object code (see object code list for possibilities).

Expected results:

  • The error message from the previous invalid code should persist.
    (For VO: User should be able to tap and listen to the error message.)
  • The number fields should clear after a brief moment (~0.5 seconds).
    (For VO: User should be able to tap on the two fields and hear them as being empty.)
  • The error message should persist.
    (For VO: User should be able to tap and listen to the error message.)
Test 6: Enter a valid object code (cont'd from Test 1, 4, or 5)

Procedure:

  1. Complete Test 1, 4, or 5.
  2. Enter a two-digit, valid object code (see object code list for possibilities).

Expected results:

  • If there was an error message from a previously invalid code, it should disappear immediately.
  • There should be a brief pause after the last digit is entered.
    (For VO: User should hear the displayed message "Opening artifact page".)
  • The screen should transition to the respective artifact view.
    (For VO: User should hear "Web page loaded - Artifact".)

Boundary Tests

Description: Ensures proper functionality at the input limits.

Protocol: Perform these tasks on the following site.

Wiki Markup
\[\] <span style="color: #ff0000">&#42;**note that this URL will change</span>

________________________________________________________

Column
width35%
Panel
borderColor#321137
bgColor#fff
titleBGColor#c1b7c3
borderStylesolid
titleSpecifications

Code entry wireframes
Code entry storycards

Panel
borderColor#321137
bgColor#fff
titleBGColor#c1b7c3
borderStylesolid
titleOn this page
Table of Contents
indent10px
stylenone