Explore topic-wise InterviewSolutions in .

We, testers work to FIND four types of common bugs; critical, block, minor and MAJOR. To EXAMPLE there, a phone system crash when testing a particular feature of the DEVICE will be classified as a critical bug. The GUI bugs will be categorized as minor bugs, and FUNCTIONAL disability of a particular feature will be submitted to a major bug list. Certain performance unavailability through the device is ON will fall into the block bug list.

• All the test CASES should be stored together source code
• While WRITING the code, developers should PREPARE the test cases at the same time.
• Testers should avoid rooted emulators and devices.
• Every time the code changed, USE of continuous integration and test execution is necessary.

The android TESTING framework includes a TOTAL NUMBER of THREE segments:

• Application Package
• Instrumentation TestRunner
• Test Package

Mobile APP testers basically use two types of automated tools,

• Object-based mobile testing tools
• Image-based mobile testing tools

Jama solution and RANOREX are two of the best object based mobile testing tools, whereas RoutinBot, SIKULI and Egg Plant can be NAMED as best AVAILABLE image-based mobile testing tools for our use.

A STANDARD ANDROID strategy could include unit testing, system testing, INTEGRATION testing, and operation testing based on the features available within the tested mobile APP. Other tests can be performed too if REQUIRED.

The WEB testing is REQUIRED for WEBSITES and PORTALS, whereas the WAP testing is needed for the network application testing.

An AUTOMATION TOOL should SUPPORT the below-mentioned features:

• Script usability
• Multiplatform compatibility
• Source code changes
• Different OPERATING system compatibility
• Jailbreak statements

• Application COMPATIBILITY CHECK on MULTIPLE devices
• The app must connect and disconnect properly every time with the change of IP address and port address,
• Repeated SEND MESSAGE to multiple devices
• Multiple browser compatibility checks

WAP stands for WIRELESS Application PROTOCOL and it ASSURES the reliability of the network. It makes sure that the targeted application can be deployed to other PLATFORMS for the testing purpose easily.

• Enter a name field
• Select target API for the list
• Enter the size
• Select the skin section
• Select create AVD
• Choose the REQUIRED AVD
• Start & launch

There are various TOOLS available in the market to record CPU performance. Testers can INSTALL apps such as Usemon, CPU Stats, CPU MONITOR, and CPU-Z for best PRACTICES and receive some advanced OPTIONS for help.

The workability of the SIMULATOR is based on SOFTWARE, and the EMULATOR is based on hardware. The simulator system behaves similarly to something ELSE while emulator system behaves LIKE something else.

The availability of defects TRACKING TOOL is just too many, but tools such as Jira, QC, BUGZILLA and RALLY can be used for best PRACTICES.

The application should be TESTED on 4G, 3G, 2G, and WIFI. Even though 2G is a SLOWER network, TESTERS should verify the application on it to track the application performance.

Yes, it’s POSSIBLE to install an SD CARD in the EMULATOR with the below given a command.
MKsdcrd –I mySDCard 1024M mySdCardFile.img

To TEST the web interface in an iPhone SIZED frame, we can USE iPhone tester. The APPIUM testing TOOL can be used to test automation in native and hybrid iOS applications. Testers used iPad Peek to test a web application using an IPad interface.

Port testing is performed to test a SINGLE FUNCTIONALITY on different devices with different platforms. There are TWO categories for this, Device Testing & PLATFORM Testing.

• High costing
• Lock-in
• Issues with INTERNET connectivity
• Subscription model
• Time CONSUMING and image-based automation
• The framework limitation while PERFORMING automation

The CRITERIA list will be as FOLLOWING:

• Installation
• The launch of the application without network
• App orientation if it supports
• App un-installation
• Application response testing
• Application performance testing on VARIOUS devices and network SCENARIO

The testing on Android Testing Framework for device or EMULATORS is difficult, and sometimes may take a lot of development EFFORT to run and build a test case, A Robo-electric framework will allow testers to run Android test directly on JVM without any NEED of EMULATOR or REAL device.

The A/B testing for an iOS APP includes three steps, which are:

• Configure a test: Preparation of two versions of targeted iOS app and the test metric
• Test: Simultaneous test of the two versions
• ANALYZE: Measure & analyze the RESPONSE to release the better VERSION