Fluid Engage browse QA test plan

Owned by James Yoon
Last updated: Jan 04, 2011 by Inclusive Design Research Centre OCADVersion comment
2 min read

Fluid Engage browse 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
On This Page
Specification
  • []

QA Tests

ProtocolPerform the following tests using each system environment

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

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


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.

[] ***Note this URL will change

Test 1: Page load

  • Procedure
    1. Open the browser and navigate to the specified URL (index page)
    2. Click on one of the browse links
  • 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

ProtocolPerform these tasks on the following site.

[] ***note that this URL will change

________________________________________________________