Fluid Engage view QA Test Plan

Environments iPhone OS 3.0 on iPhone 3G or 3GS iPhone OS 3.0 on iPod touch 1G, 2G or 3G General QA Guidelines General Use 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

ProtocolPerform the following tests using each system environment

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

Unit Tests

________________________________________________________

ProtocolLaunch the following websites to execute unit tests. []

Task Oriented Functional Tests

________________________________________________________

DescriptionEnsures that the component is able to handle expected input.

ProtocolPerform these tasks on the following site.

http://build.fluidproject.org:8095/engage/demo/index.html

Test 1: Page load

• Procedure
  1. Open the browser and navigate to the specified URL (index page)
  2. Click on one of the view links

• Expected results
  • 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 an ellipsis (i.e., "..."). If no title exists, it should read "no title".
  • If an image exists, it should appear below the header title. If no image exists, nothing should exist in its place (e.g., image substitutes, broken image icons, etc.)
  • If title exists, full title should appear below the image. This title should not be truncated. If title doesn't exist, it should read "No Title".
  • "Tombstone" information about artifact should appear below the title--this includes artifact provenance, date, accession number, etc.
  • A description should appear below the "Tombstone" information, taking up to three lines. If the description would otherwise extend past three lines, the excess should be truncated and replaced with an ellipsis (i.e., "...") and an expand button (e.g., a "+" or "more" button). If no description exists, nothing should exist in its place.
  • A collapsed "Audio and video" panel should exist if and only if audio or video assets for the artifact exist.
  • A collapsed "Comments" panel should exist if and only if comments for the artifact exist.
  • A collapsed "Tags" panel should exist if and only if tags for the artifact exist.

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: Expanding and collapsing description

• Procedure
  1. Touch the expand button on the description, if one exists (may take the form of a "+" button).
  2. Touch the collapse button on the description, if one exists (may take the form of a "-" button).

• Expected results
  • Description should expand to its fullest when you press expand. The screen should recenter such that the top of the description is near the top, if the expanded description would otherwise extend beneath the screen fold.
  • Description should collapse back to three lines. The screen should recenter so the top of the description is visible, if necessary

Test 5: Expanding and collapsing panels

• Procedure

• *# Up to three panels may be present: "Audio and video", "Comments", and "Tags".

5A. If at least one panel is present:

• *# Touch the header of a collapsed panel to expand it.
  1. Touch the header of an expanded panel to collapse it.

5B. If two or more panels are present:

• *# Touch the header of a collapsed panel to expand it.
  1. Touch the header of another collapsed panel to expand it.
  2. Touch the header of an expanded panel to collapse it.
  3. Touch the header of another expanded panel to collapse it.

• Expected results

For 5A:

• • Touching the collapsed panel header should expand it, with the screen recentering such that the panel header is near the top, if the expanded panel would otherwise extend beneath the screen fold.
  • Touching the expanded panel header should collapse it without recentering the screen.

For 5B:

• • Same as 5A.
  • Additionally, expanding the second panel while the first one is already expanded should have no effect on the previously expanded panel (i.e., no accordion behavior--two or more panels can be expanded at the same time)

Test 6: Related and visitors also enjoyed...

• Procedure
  1. Touch "Related artifacts"
  2. Navigate back to the specified URL

• Expected results
  • Activating "Related artifacts" should bring you to a browse artifacts screen.

Boundary Tests

________________________________________________________

DescriptionEnsures proper functionality at the input limits

ProtocolPerform these tasks on the following site.

http://build.fluidproject.org:8095/engage/demo/index.html

________________________________________________________