Portal Downtime
When opening the app without portal access, it should alert the user that the portal could be reached and only local modules will be shown. There should only be 3 icons on the home screen for the modules that don't require the portal.
To test this, you'll need to either shut down the portal server, or prevent your device/emulator from reaching the portal host.
Network Downtime
When the user tries to make any network request (such as loading home screen, logging in, trying to load a portlet), the app should check that they have a live internet connection. If the device doesn't have an internet connection, a simple window should appear notifying them that they don't have network access, with a button to try again. Once the user has internet connection again, if they press try again, it should take them to the home screen and load their portlets.
To test this, go into Airplane mode or disable data on the device/emulator. Once the network downtime screen has been reached, turn the network radio back on to test that the app is able to re-establish a connection.
Authentication Process
When the user first installs the app, they should be automatically logged in as a guest, and an indicator at the bottom of the home screen should explain that they're seeing a limited layout. Clicking that notification should open the settings window where they can login. After logging in successfully, they should be notified that they've logged in, and should be redirected back to the home screen where their new portlets will be loaded. At this point, the blue indicator at the bottom of the home screen should be gone. If the user returns to the settings window, they should see a new "Sign Out" button since they're now logged in.
If the user's login is unsuccessful, they should be alerted that the login failed, at which point they can re-type the credentials. If the user goes back to the home page at this point, they should still see the guest layout and blue indicator at bottom of the screen.
When the user logs out, they should be notified that the logout was successful, but the settings window will remain open.
If the user is signed in, their credentials should be saved so that next time they open the app, it loads their individualized layout (and doesn't have the blue guest layout indicator at the bottom of the home screen).
Orientation Changes
The app is designed to be rotated freely, and adapt in orientation and dimensions as the user rotates their device. The best way to test this is to constantly rotate the app each time you navigate to a new view, and rotate each view at least twice to make sure it adapts properly to the changes.
Module Testing
There are two types of modules: native and web-based. The web-based ones all use the same native code, so testing one thoroughly will tend to bring to light issues with all of the web-based portlets.
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.