...
The main feature to test with web-based layouts is a dynamic secondary navigation bar with a "back" button that navigates the user back one step in the embedded web browser. The back button should only appear on pages after the first page of the portlet. For example, when you open the videos portlet, it shouldn't show the back button until you actually select a video. The back button should remain at the top of the view until the user goes back to the videos home page.
Also in web-based layouts in Android, try using the device's hardware back button to go back in views (once you've navigated past the home page). If you're on the home page, it should exit the portlet.
Home Screen
The home screen should display a grid of icons representing portlets the user is able to use. It should also determine if the user is a guest user, and if so, display a blue bar at the bottom of the screen with white text indicating that this is a guest layout. Clicking this blue bar should take the user to the settings module, where they can log in.
If the portal isn't reachable, the blue bar indicator should have text representing that the portal wasn't able to be reached to load modules. Clicking the indicator should attempt to reach the portal again and load the user's portlets.
Map
When opening the map, the user should see a loading indicator telling them that the locations are being loaded. When the loading process is done, the map should be centered based on default location returned from the map locations web service. If there was an issue getting map locations, or parsing the data, the user should be notified of the specific issue with an alert. If the app wasn't able to parse the locations, the user will only be able to search locations that had already been loaded in the app.
When the user searches for a term, it should either notify them that there were no locations that matched the search, or it should plot points on the map for all results that match the search, and should center the map around those locations. Clicking on one of the results should first open a title of that location. Clicking that title should open a detail view of the location, which shows the address, name, and photo of the location.
Clicking "back" from the detail view should return to the map view with the search results still displayed.
- Test that you're able to exit the map, return to the map, search, and open a new result in the detail view.
- Test searching for nonsense strings (with dangerous characters and SQL injection statements) to make sure it handles gracefully.
- Try a blank search.
- Try a single letter search.
Directory
User should see any emergency contact info displayed if available, which they can click to view a detail view of contact info.
User should be able to search for one or more characters to load results to browse. Clicking any of the results should open the contact detail view.
Directory Detail View
In this view, certain fields should prompt the device to an action if possible. If the user clicks email, it should try to open a native email dialog with the address populated (if the device has email configured). If the user clicks phone, it should open the native phone dialer if possible. If the user clicks an address, it should open a web browser or native maps application with that address.
Pressing "back" in this view should return to the directory home, or search results, depending on what was opened prior to viewing the detail.
Test that after viewing a detail, you can leave the directory altogether and return to the directory home/search view, search again, and load a detail again.
Settings
Info
...
(Local, Web-based)
The info module is a web-based view, but the code is local (not loaded from the portal like the other web-based portlets).
Videos (Web-based)
Calendar (Web-based)
...