Fluid Engage my collection QA test plan
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
- Perform each of the tests under "QA 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.
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.
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:
- 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: Check empty My Collection
Procedure:
- Clear the device's Safari cache and cookies.
- Start the application.
- From the home screen, invoke "My Collection".
(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 - My Collection".)
- A screen showing an empty collection with instructions indicating that the user's collection is empty should appear.
(For VO: Instructions should be readable by VO.)
Test 2: Create a My Collection
Procedure:
- From the application home screen, invoke "Enter object code" or its icon.
- Enter a valid object code (see object code list for possibilities).
- Invoke "Collect" on the artifact view.
- Invoke the home icon to return to the home screen.
- Repeat steps 1-4 several times (say, a dozen times).
- When this is done, invoke the "Home" button to return to the application home screen.
Expected results:
- Each time "Collect" is tapped on, the button should change to read "Uncollect" and a status message should appear indicating that it was added to "My Collection".
(For VO: User should hear the status message.)
Test 3: Page load (cont'd from Test 2)
Procedure:
- Complete Test 2.
- From the application home screen, invoke "My Collection" or its icon.
- (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 - My Collection".)
- An action bar with a single action button, Send, should be visible.
- Below, a grid of thumbnails should be visible. No text should be accompanying the thumbnails.
- The thumbnails should be of the artifacts that you collected from Test 2.
(For VO: The thumbnails should have appropriate link labels giving the artifact title.)
Test 4: Tapping on an artifact in grid view (cont'd from Test 3)
Procedure:
- Complete Test 3.
- Invoke an artifact in the grid.
- Invoke the back button in the artifact view.
Expected results:
- You should be redirected to the artifact view corresponding to the artifact thumbnail you selected.
- See artifact view test plans or wireframes for further details on expected artifact view presentation.
- Upon tapping the back button from the artifact view, you should be returned to the My Collection page in grid view.
Test 5: Switching to list view (cont'd from Test 3 or 4)
Procedure:
- Complete Test 3 or 4.
- Invoke the switch to list layout icon in the top right corner.
- (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 get a feedback about the loading of objects in list layout.)
- An action bar with a single action button, Send, should be visible.
- The grid view should switch to list view of artifacts.
- Each of the list items should consist of:
- Artifact thumbnail
- Name of the artifact
- Date of the artifact
- The exact artifacts from grid view should appear in list view (no more, no less).
Test 6: Tapping on an artifact in list view (cont'd from Test 5)
Procedure:
- Complete Test 5.
- Invoke an artifact in the grid.
- Invoke the back button in the artifact view.
Expected results:
- You should be redirected to the artifact view corresponding to the artifact thumbnail you selected.
- See artifact view test plans or wireframes for further details on expected artifact view presentation.
- Upon tapping the back button from the artifact view, you should be returned to the My Collection page in list view.
Test 7: Switching back to grid view (cont'd from Test 5 or 6)
Procedure:
- Complete Test 5 or 6.
- Invoke the grid icon in the top right corner.
- (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 get a feedback about the loading of objects in grid layout.)
- An action bar with a single action button, Send, should be visible.
- Below, a grid of thumbnails should be visible. No text should be accompanying the thumbnails.
(For VO: The thumbnails should have appropriate link labels giving the artifact title.) - The exact artifacts from list view should appear in the grid view (no more, no less).
Test 8: Send the "My Collection"
Procedure:
Expected results:
Boundary Tests
Description: Ensures proper functionality at the input limits.
Protocol: Perform these tasks on the following site.
Specifications
On this page