Sunday, 1 February 2015

Posted by Sandeep Kr | 22:03 | No comments
 Mobile app testing is a process through which the application software developed for the hand held mobile devices is tested for its usability, functionality or consistency. The mobile application testing can be automated and manual type of the testing. The mobile apps either come preinstalled & can be installed from the mobile software distribution platforms.

Few questions ask in mobile testing interview with answers:

Difference between mobile application testing & just mobile testing
The mobile application testing suggests a testing the application on hand-held devices & differs from the mobile testing in that its focuses on the features or functionality of tested app only while other closely focuses on the mobile devices native app features like Call, SMS, Media Player and etc.

Can you remember names of different versions of the Android Operating System?
Sure you can remember. Here they’re:
Android 1.5 - Cupcake, Android 1.6 - Donut, Android 2.0/2.01/2.1 - Eclair, Android 2.2 - Froyo, Android 2.3 - Gingerbread, Android 3.X - Honeycomb, Android 4.0 - Ice Cream Sandwich, Android 4.1-4.3 - Jelly Bean, Android 4.4 - KitKat, Android 5.0 – Lollipop.
You might want to know more about a latest when answering this question. Among features of Android 5.0 Lollipop:
Enhanced notifications
New lock screen
New multi-tasking
New notification bar
Security - personal unlocking
Battery life - new saver mode
Performance
Android TV

What the major criteria should be taken in consideration while doing the end-to-end mobile testing?
The starting areas of the attention in this case should be installation, launch first time without a network, application’s un-installation, it’s the orientation if supported, & the testing application performance using in the different devices with the different networks scenarios. Ahead, you might want to test, how the application is responding in the case of entering invalid user credentials & attempting for change those after installation. If the application is to access network, it’s crucial to see that the logs generating during this contains the sensitive information’s in the encrypted form only.

What mobile app types do you know?
We can distinguish the three broad types of the mobile applications:
The native applications are those especially developed to a certain platform, it directly installed on the device & taking the benefits of all its features such as the GPS, camera, compass and etc. These applications utilize native notification system of the device & works offline well.
The web applications on mobiles are web portals designed & hosted for the mobile devices.
The hybrid applications can be viewed as the web applications built in native apps. They’re written using the web technologies like JavaScript, CSS or HTML. They executes inside a native container while benefits the browser engine of a device to render HTML & process of JavaScript locally. 

How one test could patches & defect fixes for an application in production?
Since, the regression testing of whole product can’t be effectively done in a short time; it makes a sense for regression test, relative module & focus mainly on the portion related to bug fixes or additionally, to do the sanity-testing on the rest of modules on high priority of devices.

Which tools can be used to debugging?
It can be done through means of iPhone Configuration Utility on iOS or Android Monitor.bat on the Android. With the log provided from these tools it’ll be easy for the developers to tell cause.

Which mobile-automation-testing tools do you know?
It means of the automation are generally chosen the subjectively depending on the project needs & app type. The good paid automation tools available: Silk Mobile, Ranorex, SeeTest and etc. There’re also eligible the free tools like Robotium, Appium, Calabash and etc., but the using of these requires certain coding-skills such as Ruby and Java.

What is it you can do with an actual device that you can’t do with the emulators?
The testing on tangible devices has a number of benefits over the emulators. Only the using of tangible devices you can test the interrupts as phone calls, messages, low battery scenarios, Bluetooth, battery drain, memory card mount or un-mount scenarios, & actual application performance as a whole.

How you can learn about application’s CPU usage or it’s the memory utilization?
On the Google-Play, you can find the tools as CPU Usage or Process List Viewer, CPU Usage-Monitor and etc. Systrace feature from the Android monitor can also help when the using of SDK.

0 comments:

Post a Comment

Bookmark Us

Delicious Digg Facebook Favorites More Stumbleupon Twitter