Monkey tools provide features like:
The types of mobile app testing includes:
To install SD card in emulator, you have to use the command
MKsdcrd –I mySDCard 1024M mySdCardFile.img
You can use various tools like Usemon,CPU Usage Monitor, CPU Usage& Process List Viewer etc available in Google Play store and if you want to use sdk, then you can use systrace feature of Android Monitor
Very first test we have to perform installation , after that we check the basic functionality and after that we check the connectivity related stuff of the application, Then we uninstall the build and verify how application respond when we interrupt during installation and also we check interruption scenarios when our application request network call .
We also do low network/poor connectivity testing during network call. Upgrade from older version to newer version. navigation in the application without network if it supports this feature.Compatibility of app on different kind of phones like having external buttons & devices do not have external buttons or other than this flip phone etc
Mobile security testing includes
We can use monitor.bat file located under tools folder of android sdk to see log and we can select and save the log from it.other than this alogcat is a free log getting tool which is present in Google Play
A/B testing for ios includes three steps:
Mobile app testing suggests testing an application on hand-held devices and differs from mobile testing in that it focuses on features and functionality of the tested application only while the other closely focuses on mobile devices’ native application features like SMS, Call, Media Player, etc.
Generally the issue depends upon the different OS/device version, it might be same thing is working on one OS while it might not work on another version.Example we faced issue that our application was working fine on iOS 6.x version devices but on tapping few modules on iOS 5.x devices application crashes and same happened with 2.3.5 Vs
We have to test the application on 2G/EDGE, 3G and Wifi network because some times application faces issues on slower networks
WAP Testing: It is the testing the WAP (Wireless Application Protocol) used in network applications
Web Testing: It is related mainly to the testing of web applications such as websites and portals
Filters helps you in finding relevant information about your application and you can create filter based on the application package name like com.abc.com and save this filter by name as My application ,when you click on this filter then you will see only logs which are from your application.
You can create filter based on Log tag which is related to the thing that line is doing example if you have placed system.out to print the output put then you can create a filter by tag System.out, then it will short list all the print output.
And you can create filter by Choreographer which helps in finding the skipped frames if you want to see it.
You can create filter corresponding to your PID and log message which is coming as text also.
The standard Android testing strategy must include the following test:
Some time some issue appear on particular version device and OS of device also do matter.
Mobile applications can be broadly categorized into three categories i.e, Native app, Web app and Hybrid App.
Native App: Native app are developed specifically for one platform, which is coded with a specific programming language (like Objective C for iOS, Java for Android) and installed directly onto the device and can take full advantage of all the device features — they can use the camera, the GPS, the accelerometer, the compass, the phone book etc. Native apps can use the device’s notification system and can work offline. Native apps are installed through an application store (such as Google Play or Apple’s App Store).Native mobile apps provide fast performance and a high degree of reliability. Example of native app: Temple Run, Candy Crush etc.
Web App:Web applications are mobile web portals that are designed, customized and hosted specifically for mobiles. They are accessed through the mobile device’s web browser using a URL. Web apps became really popular when HTML5 came around and people realized that they can obtain native-like functionality in the browser. Mobile web applications cannot use device functionality. Example of web app: google.com, m.snapdeal.com, m.yahoo.com etc.
It totally depend upon the project to project,can you please elaborate on the question because this is project specific as starting from installation and version upgrade ,uninstallation etc we do apart from functional testing. Security and Performance of application also need to be tested.
@ Performance testing of the Web service which your application uses you can use jMeter, it is an open source tool which can be used to test the api’s performances.
@Automation: It is very subjective term & totally depends on the project need and type of application , there are several paid tools available in the market like SeeTest, Ranorex, Silk Mobile etc while good free automation tools are Calabash, Appium , Robotium for Android, KIF for iOS and using free tools you require some coding skills like ruby or Java.
You can test the interrupts like phone call, messages, battery drain out completely while you were using the application under test, low battery scenarios etc on real devices , memory card mount/unmount scenarios , actual performance of you application can be test on real devices only, Bluetooth related testing can be only done on real devices.
For mobile testing, two kinds of automation tools are available to test mobile apps
We generally divide the modules among the team members and then shuffle the modules among team member with different devices.
Mobile Application Testing (MAT) is the testing of application on mobile devices and it is different from Mobile Testing (MT) in the term that in MT we focus on the native application features of the Mobile devices like Call, SMS, Media Player etc while in MAT we focus only on the functionality & features of the application under Test. i.e, MT is generally done in handset makers like Samsung, HTC, Nokia, Sony, Apple etc while MAT is done in various product based companies and through there vendors like service based companies which do testing of various mobile applications products on different devices like Gmail on mobile, Skype on mobile etc.
Critical: Your phone system crash when testing particular feature in your device
Block: Unable to do anything though phone is on unless you reboot your device
Major: Unable to perform a function of a particular feature
Minor: Under minor bugs usually GUI bugs fall.
Simulator: It is an electronic network simulation equipment or a base station equipment for CDMA/CMA mobile phones. It helps in latching home networks without roaming services and can make Voice; Data calls, SMS,
Emulator: It is a software to test mobile application without a live handset
Challenges that tester faces while doing mobile testing are:
iPhone tester: Test your web interface in an i-phone sized frame
Appium: It is a test automation tool used with native and hybrid ios application
iPad Peek: Test your web application using an iPad interface
Test Studio: It enables you to record, build and run automated tests for your iPad and iPhone applications.
ajor areas are Installation,first time launching application without having network , uninstallation of app, orientation of app if it support it , testing application performance on different kind of devices and network scenarios , testing the application response how it is responding when invalid user credentials are provided and try to change them after installation n so on.
Also if your application is accessing network then you must see the logs generated during that period so that sensitive information should always go in encrypted form, like if it is payment related CC number etc.
Android testing framework includes three segments:
Application Package: It is the target application that requires to be tested
Instrumentation TestRunner: It is a test case runner that runs test cases on target application. It includes an SDK tools for building test and a tool that provides APIs for writing program that control an android device, for example, MonkeyRunner
Test Package: It includes two classes, Test case classes, and Mock objects. Test case classes include test methods to perform on target application, while mock object includes mock data that will be used as sample input for test cases.
We generally do regression of relative module and mainly focus on the area which are related to the bug fixes as per the developer as we can not do entire regression in very short span of time, so just do sanity of rest of the application modules on high priority devices(on which you have major customer base if you have crunch of time members & if team size is not an issue do sanity on all major devices)
Testing done on Android Testing Framework for emulators or device is difficult. Running and building test case sometimes takes lots of development effort. Robo-electric framework allows you to run Android test directly on JVM without the need of a device or an emulator.
Issue is saving contact on phone memory or deleting it or some time conference call issue while an active call is there n like that.
We generally use logs to see the cause of issue where the failure is occurring , so for iOS iPhone configuration utility for Android Monitor.bat etc can be used and if you provided logs from these tools developer can easily under stand the cause of issue.
This is generally done by the Use cases, SRS and FRS document as you application specific test data can be only created using these things.
This testing is done to test the same functionality on different devices with different platforms.
It is classified into two categories:
For mobile testing, the test automation tool should have following criteria
Multi-platform support: Ensure that the tool does support your current and future target platform
Script Usability: Object-based tools provides a high degree of the script usability
Jailbreak Requirement: If the tool uses rooted devices, it may not support latest OS version and may be incompatible with MDM policies
Source Code Changes: Sharing source code may not be possible always
Lead time for New OS version: How soon tool can support new iOS/android/other OS version
Same with Android Debug Monitor (Monitor.bat) if device is connected use screen capture feature and also for Samsung device like note2: Power and Home buttons at the same time & wait for capture sound
his is of same nature like any other software testing project using any tool like Jira, Bugzilla etc