Q&A_Maturity of Mobile Test Automation- Approaches and Future Trends


Published on

Impetus webcast " Maturity of Mobile Test Automation: Approaches and Future Trends " available at http://lf1.me/Pxb/

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Q&A_Maturity of Mobile Test Automation- Approaches and Future Trends

  1. 1. Webinar: Maturity of Mobile Test Automation: Approaches & Future Trends Questions and Answers from the session March 12, 2014 Webinar recording available here Q. You said, we can record once and execute on multiple devices using mAutomate -Can I record on Android Smartphone & Execute on Tablet? A. Yes, we can record on Android Smartphone and execute it on Android Tablet – if you are targeting the same application built for both the form factors. The test scripts generated by mAutomate are independent of device screen size, resolution and form factors. Q. How do you deploy the iOS builds Over-The-Air on the test devices without going through the app Store? A. We need the UID of the test device to be added in the iOS developer certificate with which the test build is generated and placed on any OTA server. This OTA link is provided to the mAutomate device agent on the test device at the time of execution, which downloads and installs the test build on it. Q. What type of apps & platforms are supported by mAutomate? A. mAutomate Supports - Native, Hybrid & Web apps running on Smartphones, phablets & tablets which are Android 2.3 onwards, iOS 4.1 onwards and Windows Phone 8 (support is coming soon...) Q. Can mAutomate load the captured test results to Quality Centre? A. Yes, mAutomate supports integration with Quality Centre, Bugzilla and Hudson/ Jenkins – CI. Q. Does mAutomate simulate devices, OS's, or browser versions? A. No, it simulates only environmental conditions like Network Signal Strength, device rotation and interrupts based on the need of test cases during execution, matching to that at the time of recording. It is recommended to test the applications, on real devices of the target OS & browser versions, on which you expect your customers to be using it.
  2. 2. Q. Do the testers have to have access to the physical device(s) to create/run the automation? A. The testers can execute the test scripts on multiple remote devices without having any physical access to them (though all such devices should have been already installed and running mAutomate device agent). For recording/creation of test scripts, the QA needs to have access to 1 device/emulator – on which it can execute the app flows manually for recording. Q. Can I modify the code generated by mAutomate? A. Yes, mAutomate provides the facility to edit the test scripts with the help of very intuitive GUI based test script editing support on the web interface. Q. Do mAutomate use some scripting languages while script editing or it simply use the recorded script language (may be human readable)? A. Yes, for advance QA users – test scripts are available on the web interface in human readable format and a GUI based test script editing support is also provided. Q. What is the automated test output format like HTML, PDF? A. Reports are available on the web as well as on PDF’s. These are provided to the QA engineer on his email id after every execution. Q. Can the scripts be executed on different platforms example completing a form in an android device and after that completing it in iOS? A. Yes, in case of Mobile applications – we can record the test scripts on one platform and execute it simultaneously on multiple platforms because it’s the same app running on all different platforms. For Native application, we need to record the test scripts for each platform separately.