Fluid Engage an exhibition, catalogue 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: Catalogue page load
Procedure:
- From the application home screen, invoke "Exhibitions" or its icon.
- At the Exhibitions page, invoke "Simply Montreal" exhibition.
- At Simply Montreal main page, 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 objects should appear in grid view.
- At the top of the page, a "View all objects" option should appear, with the number of objects in the catalogue.
- If the exhibition has themes, the objects will appear included in these themes.
- Each object is represented by a thumbnail link. The name of the object doesn't appear.
(For VO: User should hear a link label indicating the name of the artifact the thumbnail is linked to.) - If the object hasn't any image available, an icon "no image" should appear instead of the thumbnail.
- There should be a maximum of 4 objects per row.
- A "View all in (the theme title)" option appears at the bottom of each theme, with the number of objects included in that theme.
Test 2: Switch to list view (cont'd from Test 1)
Procedure:
- Complete Test 1.
- Invoke the button at the right side of the navigation bar (switch to list layout button).
- (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 a message about the loading of objects in list layout.)
- The exhibition objects should appear in list layout.
- At the top of the page, the "View all objects" option should remain, with the number of objects in the catalogue.
- If the exhibition has themes, the objects will appear included in these themes, one below the other.
- Each object takes a row. Each row contains a thumbnail at the left side, and the object's name and a secondary information (usually date) at the right.
- If the object hasn't any image available, an icon "no image" should appear instead of the thumbnail.
- A "View all in (the theme title)" option appears at the bottom of each theme, with the number of objects included in that theme.Â
- The screen should display the same themes and objects as in the grid layout.
Test 3: View an object's information (cont'd from Test 2)
Procedure:
- Complete Test 2
- Invoke one of the objects (anywhere on the row).
- (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 object should appear in the navigation bar, in that order. No other elements should be present on the bar.
- Information about the selected object should appear on the page.
Test 4: Back to the main catalogue page (cont'd from Test 3)
Procedure:
- Complete Test 3
- At the object's page, invoke the back button (at the left side of the navigation bar).
- (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".)
- The main catalogue screen should be displayed in list view (consistently with the list view at the test 2).
Test 5: Switch to grid view (cont'd from Test 4)
Procedure:
- Complete Test 4.
- Invoke the button at the right side of the navigation bar.
- (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 a message about the loading of objects in grid layout.)
- The right button at the navigation bar should now become switch to list layout button.
- The exhibition objects should appear in grid view (same screen as in the Test 1).
- The screen should display the same themes and objects as in the previous list layout.
Test 6: View an object's information (cont'd from Test 5)
Procedure:
- Complete Test 5
- Invoke one of the objects (any thumbnail).
Expected results:
- (For VO: User should hear "Web page loaded - Artifact".)
- A back button, a home button, and the name of the object should appear in the navigation bar, in that order. No other elements should be present on the bar.
- Information about the selected object should appear on the page.
Test 7: Back to the main catalogue page (cont'd from Test 6)
Procedure:
- Complete Test 6
- At the object's page, invoke the back button (at the left side of the navigation bar).
- (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".)
- The main catalogue screen should be displayed in grid view (consistently with the grid view at the test 5).
Test 8: View all objects in the catalogue (grid view)
Procedure:
- Load the catalogue main screen. Ensure you are at the grid view.
- At the catalogue main screen, invoke the option "View all objects".
- (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 - Browse Artifacts".)
- 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 objects should appear in grid view (4 objects per row).
- The title "Viewing all objects" + number of objects in the catalogue should appear at the top of the page.
- Each object is represented by its thumbnail. Its name doesn't appear.
- (For VO: User should hear a link label indicating the name of the artifact the thumbnail is linked to.)
- Objects are displayed without categories (themes don't appear).
- If there are more than 20 objects, a button to load 20 more objects appear at the bottom of the page.
Test 9: View all objects in the catalogue: switch to list view (cont'd from Test 8)
Procedure:
- Complete Test 8.
- Invoke the button at the right side of the navigation bar.
- (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 a message about the loading of objects in list layout.)
- The right button at the navigation bar should now become "switch to grid layout" button.
- The exhibition objects should appear in list view, without themes.
- Same objects as in the grid view should be displayed.Â
- If there are more than 20 objects, a button to load 20 more objects appear at the bottom of the page.
Test 10: Back to the main catalogue screen (cont'd from Test 9)
Procedure:
- Complete Test 9.
- Invoke the back button, at the left side of the navigation bar.
- (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".)
- The main catalogue screen should be displayed in list view (consistently with the list view at the test 9).
Test 11: View all objects in a theme (grid view)
Procedure:
- Load the catalogue main screen. Ensure you are at the grid view.
- At the catalogue main screen, invoke the option "View all in..." one of the themes.
- (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 - Browse Artifacts".)
- 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 theme objects should appear in grid view (4 objects per row).
- Â
- The title "Viewing all objects in" + theme name + number of objects in the theme should appear at the top of the page.
- Each object is represented by its thumbnail. Its name doesn't appear.
- (For VO: User should hear a link label indicating the name of the artifact the thumbnail is linked to.)
- Objects are displayed without categories.
- If there are more than 20 objects, a button to load 20 more objects should appear at the bottom of the page.
Test 12: Load more objects (grid view) (cont'd from Test 11)
Procedure:
- Complete the Test 11
- At the bottom of the page, invoke "Load 20 more objects".
- (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 a message about the loading of 20 new objects.)
- 20 more objects should appear following the previous ones.Â
- The new objects should appear in grid view.
- The previous objects should remain in the page, keeping the same order they had before.
- The rest of the page should remain the same.
- If there are more objects, a button to load 20 more objects should appear at the bottom of the page.
Test 13: View all objects in a theme: switch to list view (cont'd from Test 11)
Procedure:
- Complete Test 11.
- Invoke the button at the right side of the navigation bar.
- (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 a message about the loading of objects in list layout.)
- The right button at the navigation bar should now become "switch to grid layout" button..
- The objects should appear in list view, without categories.
- Same objects as in the grid view should be displayed.Â
- If there are more than 20 objects, a button to load 20 more objects should appear at the bottom of the page.Â
Test 14: Load more objects (list view) (cont'd from Test 13)
Procedure:
- Complete the Test 13
- At the bottom of the page, invoke "Load 20 more objects".
- (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 a message about the loading of 20 new objects.)
- 20 more objects should appear following the previous ones.Â
- The new objects should appear in list view.
- The previous objects should remain in the page, keeping the same order they had before.
- The rest of the page should remain the same.
- If there are more objects, a button to load 20 more objects should appear at the bottom of the page.
Boundary Tests
Description: Ensures proper functionality at the input limits.
Protocol: Perform these tasks on the following site.