Click to search on your search term.
Subscribe to Fig Leaf Tutorials


Need help with a project? Contact us at sales@figleaf.com.
From code reviews to project "jumpstarts" and full life-cycle development, we've got you covered!
Check out our case studies!
Follow us on Twitter!
Click here to join our Facebook group!

Ready to upgrade your skills? Try these instructor-led classes in Washington, DC:
Ext JS 6 Bootcamp
12/04/2017

Testing with Simulators and Emulators

Page of 168

Clearly there is no better test for your applications than actually executing them from your targeted devices. If your device is on the same wireless network as your development machine, you should be able to access your development web server by its local IP address and port number - contingent on your machine's firewall settings.

Notwithstanding the above, the iterative and fast-paced nature of debugging and troubleshooting does not lend itself to testing with physical devices. Typically, developers of mobile applications use a variety of simulators to enhance their productivity while reserving testing on physical devices for final QA processes.

The following device simulators generally provide acceptable results for initial debugging:

  • Apple Safari and Google Chrome to simulate iOS
  • Ripple - a plugin for Chrome that simulates physical device behaviors.
  • The Cross-Platform Android Simulator in the Android SDK
  • The iPhone/iPad simulator included with Xcode from Apple
    (OS/X only)

Simulators and Emulators

Page of 168
comments powered by Disqus