/
Fluid Engage an exhibition, home QA test plan
Fluid Engage an exhibition, home 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: Main exhibition page load
Procedure:
- From the application home screen, invoke "Exhibitions" or its icon.
- At the Exhibitions page, 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:
- The name of the exhibition (in a bigger text size).
- A brief introduction.
- Opening and closing dates (or the literal "Permanent exhibition").
- A "Read more" option.
- Then information about the Catalogue should appear. This should include:
- The title "Catalogue" followed by the number of artifacts in the catalogue.
- Some artifacts, each with its thumbnail (as a link) and its name below. There should be a maximum of 4 artifacts per row.
(For VO: The thumbnail links to artifacts should have a label indicating the name of the artifact they are linked to.) - A "View the full catalogue" link.
- 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:
- Complete Test 1.
- Invoke "Read more" option.
- (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.
Test 3: View the full catalogue (cont'd from Test 1)
Procedure:
- Complete Test 1.
- Invoke "View the full catalogue".
- (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 - 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 artifacts should appear in grid view.
- (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:
- Complete Test 1.
- Invoke an artifact in the Catalogue section directly.
- (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.
- 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.
Specifications
On this page
, multiple selections available,