3 responses

  1. Stephan
    June 19, 2013

    One other way to test (well, actually automatically check, but that’s another discussion) on many different devices is https://appthwack.com/.

    • Trent Peterson
      July 11, 2013

      Thanks for the mention, Stephan!

      I agree with the overall gist of this article. Emulators/simulators have a place in testing and that place is very close to development. From a test and QA perspective, though, carrier and OEM modifications, performance differences, environmental factors, etc. require physical hardware to accurately gauge how a real-world customer will experience your app.

      Sure, actually obtaining real hardware is expensive and time-consuming, but to your (Stephan’s) point, there are other options out there – options that don’t require 100 people to run tests on 100 devices in parallel.

      I’ll leave the automation discussion for another time as well, but for the UI and UX testing described in this article I’ll definitely say real people with real devices is the way to go. Of course, to free up time for that you might need to *cough* automate some of the mundane tasks you’d otherwise be busy performing.

  2. neha bapna
    January 13, 2015

    Do you have any plan for Webinar session on ‘Performance and Load testing of IOS mobile application’ ?

Leave a Reply




Back to top
mobile desktop