Testing mobile web applications

Using TestArchitect, you can create and run automated tests for mobile web applications.

CAUTION:
For power-saving purposes, computers are often configured to go into a non-active state (such as sleep) after a certain period of inactivity. By default, the processes associated with automated testing are typically not treated as “activities”, in this sense. Hence, for long execution runs, especially unattended ones, it is important that any machines serving as test controllers be configured not to lapse into any non-active mode during the test period. (Typically, your computer's power policy is configured through its Control Panel, System Preferences, or command line, depending on the platform. For details, see your system administrator or information specific to the machine's operating system.)

Supported mobile browsers

  • iOS:
    • Safari (on both iOS devices and Apple's iOS simulator).
      Remember:
      • Before testing Safari on iOS devices, you must set up and configure the mobile test device. (Learn more.)
      • Before testing Safari on the Apple Simulator, you must set up and configure the simulator. (Learn more.)
    • WebView (on iOS device) a software component used to embed web content in a mobile application.
      Remember: Before testing a web view on iOS devices, you must set up and configure your mobile device. (Learn more.)
  • Android:
    • Android devices:
      • Google Chrome.
        Remember: Before testing Chrome on Android devices, you must set up and configure the mobile test device. (Learn more.)
      • WebView, a component used to embed web content in a mobile application.
        Remember: Before testing a web view on Android devices, you must set up and configure your mobile device. (Learn more.)
    • Android emulators, including Genymotion and Android virtual device (AVD), packaged with Android SDK: