Anshuman Chatterjee | Posted on July 25, 2017August 3, 2023 | 2 min Read

Mobile App Testing Tools to Improve App Quality – pCloudy Tutorial

Mobile App Testing Tools to Improve App Quality

Mobile is the key to the digital world in today’s era. The rise of Mobile Internet has ensured that we all are going to make most of our digital decisions on a Mobile device (primarily using an App). Mobile Apps are going to be everywhere.

One of the biggest challenges for App Development teams is to ensure that their Apps works on the variety of devices. They need their apps tested on multiple devices before it is released to the market, simply because of the plethora of devices available in the market.

Each mobile from each OEM (Original Equipment Manufacturer) with different specifications is a unique device where the application should be tested.

Practically it is not possible to test the application on each and every mobile device available in the market. But the app must be tested on a large set of the devices depending on the market segment of App under test.

Introduction:

pCloudy is a cloud-based remote mobile app testing platform which allows testing of Android and iOS mobile applications on remote REAL devices. It allows the user to do Manual testing and also facilitate to run test automation on multiple devices in parallel.

It provides a whole lot of statistics like session video, device logs, Screenshots, data usage, memory usage, CPU usage, battery consumption and frame rendering count. The devices are also equipped with Real Operator SIM’s to make MO/MT calls and can receive and send SMS.

Preparing for Manual Test

Before we start the test on pCloudy, we recommend uploading the test application, test data or even test suites to the cloud drive provided by pCloudy. This is the secured location for each user.

Click on the Upload button and select the file from your local system through file explorer. After selecting the file select upload and the file will be uploaded to your cloud drive.

You can also manage the cloud drive by download. These applications can be installed on the devices as explained below.

Performing Manual Test remotely

Based on test requirement, you can search for any specific device by using the filters provided at pCloudy.

(Note: Click on any image for enlarged view)

You can access any device for Instant Access. Also, you can book the device for a longer duration for your planned testing using “Book your Device” link.

After selecting the device just click on the “Connect to a device” button to connect to the device. The below device page will be displayed with all the supported features.

The device is displayed in the middle pane with some features on the right, left and top pane.

The Left pane where the device information is displayed, followed by other tabs like App/Data, Device Settings, Debug and Automation
The top pane with handy features & a timer to show the remaining time & wake up the device and release the device back to the cloud.
The right pane to view the device logs and Performance vitals for application under test.

How to Install the application on the Remote Mobile device?

Install from my App data – enables user to upload app on device.
Push to Device – This feature allows you to transfer your test data to the device.
Upload App – Upload and install an app from your local system.

Once the application is installed you can test the application on REAL Remote Device the way you test the application with the phone in hand. You can use the mouse to give touch gestures to the device. You can click the button, drag the screen or double tap the image.

While doing functional testing on the remote device, you can also monitor the device logs next to the device. Please start the logs from the right page and start monitoring the logs next to the device.

All Mobile App Testing tools at one place: One of the biggest advantages of pCloudy platform is it provides performance statistics like Memory Usage, CPU Usage, Battery usage, Data usage & frame rendering count of the application under test without any extra efforts by the test engineer.

To view this vital statistic on pCloudy platform, please select Performance tab -> Choose an APP -> Select the application under test.

Start navigating through the application to complete the function test flow.

On the right pane, you will start seeing the important vitals of the performance.

On the left pane, you can expand the device settings. All the important frequently used applications are made available to use on the device.

You can perform below actions on the remote device:

Reboot the device remotely
Toggle the Wi-Fi connection
Adjust the volume of the device
Manage the Apps
Open Developers options
Open Play store
Open Device settings
Use Set Phone Location

If your application under test is a location aware app and if it reads the geo-location from the device to provide the necessary results, “Set Phone Location” feature can be used to inject any location on the earth to the device and the device will be teleported to the selected location.

Once you select the “Set Phone Location”, the platform shows the google maps and you can select the location of your choice on this map. The same location is injected to the device.

Other key features during manual tests

You can capture high-resolution screen shots with the skin of the device
Change the orientation of the device to Landscape and portrait
Open the browser from the list of preinstalled browsers
Use the extended keyboard if you want to enter some text on the device. However, for Android ver 5.0 and above you can directly enter the text from your system keyboard.
Check the stack trace (crash logs) if the application is crashed
You can navigate the application with the buttons
Zoom in/out the device shown on the screen
Reset the zoom level to bring the device to default size
Extend the session if the device is available
Wake up the device from sleep mode or push the device to sleep mode
Release the device back to the cloud

Reporting

Under reports folder, you can see the entire device session data for all the devices you used. You can find Videos & Logs (by default platform generates), screen shots and performance data if selected by the user.

Running test automation remotely

pCloudy platform supports test automation on multiple devices in parallel. Below test frameworks are supported for Android platform.

Monkey Test
Espresso

Calabash
Appium

You just need to select the Test platform, Choose the application under test, Test Suite, time to run on single device and test cycle name.

The biggest advantage of this platform is it generates performance vitals for your test automation scripts without you adding any hooks in your scripts. Otherwise, you will be using multiple mobile App testing tools to achieve the same result.

Once the above data is provided, user can select the devices on which the test automation to be run. Once the devices are selected, the user can schedule the test cycle.

The platform will book the devices on your behalf and will start the test automation as soon as the devices are available. Once the execution is over, the user will be notified with an email and user can see the test reports.

APPIUM Test Automation

You can run the Appium test automation scripts directly from Eclipse or Android Studio. The platform provides the plugin for both the IDE’s. Simply copy a small piece of code to your driver code and run the project, select the devices on which this tests to be run.

The “LIVE VIEW” feature will allow you to monitor the test automation runs through video streaming on the platform.

LIVE VIEW

Live view – To see the automation happening on devices

Automation Test Reports

All the test automation reports will be available under Reports folder.

The reports will open in another tab with video, logs and performance data.

To view the performance data for each device, please click on the device icon for each device.

Opkey Integration

pCloudy has seamless integration with OpKey, which is a zero code multi-channel automation tool. A unique combination of Mobile App Testing Tools for manual and Automation testing.

OpKey allows single click recording and generation of automated scripts for Mobile Apps.

You can run the automated scripts on multiple devices on pCloudy directly from OpKey interface.

Advance Features:

pCloudy also provides many advanced Mobile App Testing tools like Network Virtualization Tests, Device Tunnel (access of devices from Developer IDE and Jenkins Integrations).

Conclusion

The quality of App is extremely important for its success in the market. Right devices and right mobile App testing tools are critical ask from every Mobile Dev and Test team. pCloudy with its comprehensive set of devices and tools could be a perfect companion to every Developer and Tester.

Shivani Sinha | Posted on June 23, 2017September 5, 2022 | 2 min Read

Testing The Battery Drain For Android App

Android App Testing

If you are anything like me, you’d agree that the armor of present day mobile phone technology has a few chinks on it. Nothing is worse than applications draining the battery resources of your mobile device faster than you can fill it back up. The sunnier side of course, is that you can create teachable moments for your kids better by hiding their phone chargers and watch the colors drain from their faces.

Studies show that battery life is a top priority for smartphone buyers. In fact, just recently, an IDC survey showed that 56% of Android buyers, 49% of iPhone buyers and 53% of Windows Phone buyers said that battery life was a key reason when they bought their particular device.

It is rare to find mobile app testing tools that assure proper usage of resource by the mobile app as, included in the overall test plan and strategy.

It’s rather a tedious and long process for conventional mobile app testing methods and as such, Let us talk about how resource consumption as an app takes top priority, because nothing stops a user to uninstall their resource draining apps from their phone. Also we’ll talk about how developers and testers efficiently test mobile apps for Android applications.

Figure 1: IDC Survey

Why battery testing is important:

Thousands of new mobile apps are being launched every day. And these apps have gone beyond just utilities, games and shopping apps, nowadays, apps need to be integrated into self-driving cars, digital assistants, wearable devices etc. Billions of users need to install apps that are not only compatible with their varying devices, but also provide quality experience of the app so that it doesn’t prompt the user to uninstall it and move to an alternate app.

When you get worried about potential battery abuse, its fair economics to identify the markers that can cause increased consumption of energy by the mobile application. Critical are the functionality, usability, performance and security to make sure that the app does what it was meant to do, seamlessly. The growing need for perfect enterprise and consumer apps and the continuous need to upgrade the application to match it with what the consumer exactly wants is a job that creates high pressure for developers and testers alike, who are responsible to delivering them.

We would get deep into the best practices and tactics that should be kept in mind while testing for battery drain in your mobile app in a later blog post. For now, let us look at how developers can test for battery consumption during Android App Testing.

How to test battery consumption for mobile apps:

So far there hasn’t come a good automation method to test app battery drain. So testing Real Mobile Devices meets many requirements for efficiency in the process. Let us check out a few parameters to test battery drainage due to mobile apps.

Battery test flow
This will vary based on the functionalities of the applications. But overall the below approach or points should be considered while testing for battery consumption.
- Check the status of the battery before the test begins
- Enable the location services for the application if app supports
- Start the data sync of the application if app supports
- Start the streaming service of the application if app supports
- Check if the application send/receive the data when in the background
- Check if the application send analytics to its server
- Observe the battery consumption while doing above supported features by your application.

This will give us an idea as what is the battery consumption by the application.

Testing as end user

It is very critical to test the environment needs of the app from a real user perspective. Environments like device types, operating system, background popular apps installed and running, network conditions (WiFi, 2G, 3G, 4G, Roaming) as well as diverse set of devices with different battery states, brings DevOps teams as close as they can come to end users.

Android App Testing across varying devices

Android is guilty of OS fragmentation due to its open approach to OEM vendors. Different devices have varying battery capacity and each loses its battery chemistry over time, negatively impacting performance and battery hours. This is why we must check the battery consumption for the mobile app on variety of mobile devices. The best practice is to use multiple devices from device labs/ device clouds.

Different tools available in the market.

Android’s built in Battery App

Your Android Mobile Phone has a ubiquitous battery testing resource, as it comes preinstalled on all Android mobile devices. Android’s native battery analyzer, for example, (Settings> Device> Battery) is built into Android’s OS and helps analyze each app and let you know which are the ones draining the most fuel.

Commercial Battery Saving Apps

There are a few commercial Android Battery Analyzers which are available for free in the market, like:

GSam Battery Monitor can reset testing cycles as you go, which means there is no need for draining and recharging the battery like in android’s native battery app, and monitor app power usage without having to wait to get an information reset.

Clean Master on another hand, lets you know through its notification feature as and when an app is causing the phone’s battery/CPU to drain, which gives instant information on any CPU overuse.

pCloudy platform for Testing Battery Drain

pCloudy platform allows comprehensive features for Android App Testing. Moreover, Using pCloudy’s platform, one can monitor the battery consumption by the application. additionally, the user can also monitor memory, CPU and data consumption by the application.

The user can do the complete functional app testing on the application by touching all the critical/non-critical paths in the application. The pCloudy platform provides the necessary data for the work flow.

Conclusion

Google has said that this year their focus is on the ‘vitals’ of mobile phones, battery being one of the critical four. It’s always best to use varying angles of attack to test your app’s battery usage. And the only way to do that right now is to cover as many mobile device variants in the market and test against them.

To check battery consumption during Android App Testing Click Here.

Get 180 Device Testing Minutes Free

Avinash Tiwari | Posted on August 28, 2016September 5, 2022 | 2 min Read

Robotium Automation Execution

Robotium automation testing tool for Android

pCloudy allows you to run your Robotium test script over android devices. Robotium is an open-source test framework for Android applications.

Here are steps to run Robotium test script over android device:

Login over www.pcloudy.com with your registered Email ID & Password
Go to the Automator Page
Select Android OS version & Manufacturer
Select and add desired device
Choose Robotium (to run Robotium test scripts)
Select Application .apk file (the App to be tested)
Select Test Script .apk file (the Test Script developed for testing)
Enter Single Device execution Time (Time required for the entire script to be executed on single device)
Enter Name of your Test Cycle (this name will represent your Test Cycle)
Click on Schedule Test Cycle

In the next step, you need to confirm schedule of test automation. Here, you can see your selected application, test script, device etc.

Further, you get a pop up message of test automation schedule confirmation.
Click on OK to proceed.

Finally, you get Cloud Automator Report of your scheduled test automation.

Avinash Tiwari | Posted on July 6, 2016September 5, 2022 | 2 min Read

Testing Mobile Apps on Different Networks

Testing Mobile Apps

If you are someone using a smartphone to get through most of your day, then I’m sure would you’ve experienced it – You are in an elevator using your smartphone trying to find a restaurant for dinner but the app you are using unexpectedly crashes, or you are in a crowded subway using your smartphone to upload a video to some social media portal but the app you are using takes too long to respond, or you are just waiting for a friend in the basement of a parking lot and in the meanwhile you decide to shop for some new shoes but the e-commerce app you are using does not respond the way it should. Isn’t it frustrating when the apps you are using does not work when you require it the most? In these situations, the first thing you do is simply uninstall it, or in the worst case write a bad review.

Strangely, though most of the apps are functional and performance tested, they are still found to be defective by the users. It could be possible that not all scenarios are covered during testing. So, where is the gap? Deeper investigations have revealed that mobile apps behave differently in different network environments. In the above scenarios particularly, it seems like there is more evidence indicating that these issues are caused due to irregular mobile networks in locations such as the Elevator, or the crowded Subway, or the basement of a parking lot.

Why do apps behave differently in different network environments?

The network has a huge impact on the behaviour of your apps. Most of the apps that we use today are functioning by constantly communicating and fetching information from some servers or users that are miles away. The communication that happens is on wireless networks that are unfortunately not always reliable or consistent. Though most MNOs have established wider and better networks, it is practically difficult to achieve absolute seamless connectivity with excellent signal stability using existing wireless technologies. This is because, inherently, wireless networks have several inconsistencies like the lack of bandwidth in some places, the drop in packets caused by handovers and routing while moving, and more interference from other networks. Additionally, the networks through which data is transferred wirelessly also vary based on the technology used like GPRS, UMTS, HSDPA, LTE etc.

Why should apps be tested in different network environments?

The unpredictability of wireless networks has a huge impact on the functionality, performance and user-experience of an app. This is why we often see certain functional defects, performance defects, and sometimes crashes only when the app is running on a certain network or in some specific locations. Besides, mobile apps are expected to function on everything from an excellent Wifi connection, to a snail-paced 2.5G connection. Hence mobile apps have to undergo a wide range of tests on different networks with a variety of conditions before they are released to the users.

Are you testing your apps on different network conditions?

Traditionally, mobile apps are tested using the best networks in perfect conditions. But in real environments when the apps are being used anything can go wrong – the network bandwidth might not be enough, the latency might be high, data losses might occur, or there might be interference from other networks. App development companies have now realised the impact a network can have on their apps and are slowly filling up the gaps in mobile app testing. They are now focused on ensuring the app’s functional stability and relentless performance despite network inconsistencies. But testing mobile apps on different varieties of networks with a range of uncommon conditions is overwhelming and challenging. Moreover, these apps have to be tested on numerous mobile devices. It’s a tedious but crucial task. Additionally, tools that support such testing are scarce.

How can you test your apps in different network environments?

Testing Mobile Apps using live networks – Live networks can be used for testing mobile apps. The apps can be installed on real devices and can be tested on various networks like GPRS, UMTS, LTE, CDMA, etc. But the procedure of using real networks for app testing is slow, cumbersome, and mostly provides inaccurate results. Testers need to travel to different locations or wait for the network conditions to occur for conducting the tests. Furthermore, when the developers try to reproduce the bugs in order to fix it, the exact network conditions are hard to be replicated; eventually, most of the bugs will be closed as “Cannot Reproduce” while the bug still remains.
Simulated networks – Network related tests for mobile apps need not be such a hassle if the testers are given full control of the network being used. Using a simulated lab network, testers can easily test their mobile apps by simply selecting and applying the type of network profile to be used. They can also create and customize different network profiles by simply changing parameters like Uplink Bandwidth, Downlink Bandwidth, Latency, Loss Percentage, Packets Corruption, etc. This setup helps testers to replicate a myriad of network conditions for testing mobile apps.
On a larger view, when a mobile device cloud like pCloudy is being used you can test your mobile apps on varieties of networks, on hundreds of real mobile devices in parallel, through manual tests or automation runs. It is one platform that takes care of your entire app testing needs by helping app developers to easily test and experience the app functionality and performance on different networks and different mobile devices.

Avinash Tiwari | Posted on May 23, 2016September 5, 2022 | 2 min Read

iOS Beta Testing Using TestFlight

Introduction to iOS TestFlight

TestFlight is an online service used to distribute and test beta iOS applications. Developers can use Test Flight to evade the Apple’s bitter binding procedure for testing new versions of their apps. It provides over-the-air installation, testing, tracking and managing of Beta apps. In simple words, TestFlight acts as a link between the developer, the tester, and the Apple Developer Center.

How is it useful?

Distribution of the app over-the- air to Testers
Tracking and managing testing using TestFlight’s dashboard
Receiving feedback from testers to improve the app
To obtain reports about the device models, OS version used while testing the App
Automatically records any crashes the testers encounter and sends it to the Developer

This tutorial will walk you through integrating TestFlight into your own apps.

What do you need to start?

You have to have your certificates, app ID, and provisioning profiles in place before distributing your apps using Test Flight. Here’s the list of items you need:

A Developer ID to login to your developer account.
A Certificate for Distribution to export builds and distribute apps
An App ID
A Device UDID
Ad Hoc Provisioning Profile to distribute your app on testers devices
Sign your app with a valid ad hoc provisioning profile

These items will help you obtain an .ipa file that can be distributed for testing in iOS devices with UDIDs mentioned in the provisioning profile of the app.

Uploading your app for Beta Testing

Open up your project in Xcode, make sure you have a correct Bundle Identifier and that you’ve chosen the correct Distribution Certificate:

Choose Product\Archive from the top toolbar:

Once Xcode finishes archiving your project, click the shiny blue Submit to App Store… button:

Choose your development team

Hit Submit

Wait for your build to upload. Once done you will receive a “Submission Successful message”

Inviting Testers

Avinash Tiwari | Posted on May 6, 2016August 3, 2023 | 2 min Read

Test Your Apps on Real Devices Using Cool Plugins

Test Apps on Real Devices

Using Eclipse or Android Studio to code your app? Now with just a few simple mouse clicks test apps directly and in parallel on multiple real mobile devices.

Eclipse and Android Studio are two popular IDEs for mobile app development. The reason behind their popularity is, these are open source tools and have a great community of developers whom you can turn to for any support. Anyway, if you are one of those mobile app developers using these popular IDEs then there’s good news for you!

What if you could extend the capability of your IDEs to improve the quality of your apps? What if you could test your app on hundreds of mobile devices right from your IDE? What if you could with the help of simple plugins take your mobile app development process to a whole new level?

Well, you can – with a simple yet salient solution from pCloudy.com. With a cloud based device lab, pCloudy is contributing to the cause of redefining mobile app testing by providing remarkably useful platform and plugins to test your apps on real mobile devices. As mentioned in our previous articles, it is not enough if mobile apps are tested on Emulators alone. We need to ensure that the apps are tested on Real Devices as well. It is also important to test your mobile apps on different devices based on a carefully analysed device matrix to hit maximum downloads. To continuously develop, integrate and release mobile apps in your DevOps environment such solutions are crucial.

Here’s how can our plugins benefit you

Description:

Our Plugins act as a wizard that allows you to:

extend the ability of Eclipse to use real devices over a cloud platform
select and install an app from a Cloud Drive or from local
select multiple real devices from a cloud (Public, Private, On-premise) to test your app
run test scripts in parallel on multiple devices
perform Automation or Manual Testing

How does it work?

If you have already created Test Scripts ready for Test execution, then all you need to do is to select some real devices over the cloud platform and run the execution to test your app. To help you out with this, the Plugin generates a pseudo-code that can simply be copied into your existing test scripts using Android Studio or Eclipse. With simple changes in the test script, the app will get installed and test execution is performed on the selected mobile devices. In the end, a detailed automation report will also be generated through our platform.

With these plugins app developers and testers can:

choose from hundreds of mobile devices to test your App
effortlessly test their apps directly on real mobile devices
can view or perform an activity on mobile screen from directly within on your IDE
perform automation runs in parallel on multiple mobile devices

Download and install the plugin:

Avinash Tiwari | Posted on March 7, 2016September 5, 2022 | 2 min Read

The Smartest Way to Choose the Right Testing Platform for Your App !

Choose the Right Testing Platform

As a mobile app maker, how sure are you about the success of your app? A small failure to recognize bugs can cost you thousands of dollars! A small mistake can turn you into a big failure among the users. Now, the question is, how to choose the best platform for testing.

Every mobile application is created differently from the other and the right platform to test can be the most important reason for your app’s success.

Choosing the right platform among the various competing ones require a set of clear evaluation.

The nature of the targeted audience for your app. This will define the device matrix you should be targeting for your App Testing. Does that platform provide right device matrix for your testing needs?
Cloud based vs in-house setup – Does you testing process allow Apps to be allowed on outside cloud? Does your App have functionalities which work with in a secured network?
Type of Testing required for your App – Whether your current testing is manual or automated? Does your App require non-functional Testing?
Reliability and Scalability of the platform- Can it scale with your needs? Can the platform integrate with your existing tools and frameworks?
Return on Investment

Criterion	Description
Device Fragmentation	Can the platform handle you need of devices?
Availability	How critical for you instant availability of devices. Is you testing planned?
Automation	How much of testing is done using Automated scripts? Does the platform support the Automation tool that you are using or planning to use.
Type of Testing	What all functional features that you need to test? Does your App require non-functional Testing?
Extensibility ( integration with in-house frameworks)	Can the platform integrate with your in-house frameworks ( Automation, Test Management , Bug Management etc..)
DevOps	Can the platform support DevOps? Can it integrate with your build systems/dev IDEs or continuous integration systems.
Security	Can you upload your app on an external cloud? Does you App require interaction with your internal server?
Usage level and Cost	What is the usage pattern of your test and developing team and what is your budget?

pCloudy provides the necessary tools for convenient, effective and immediate mobile app testing. Our device is based on cloud and it enables continuous development and testing on real devices. Our unique debugging feature recognizes potential errors that will significantly reduce costs and time. Our platform provides single-click access to end numbers of real Android and Ios devices.

To experience the best with your app, we have developed three different types of cloud environments for you.

Public Cloud

With pCloudy’s publicly accessed cloud, you can perform tests directly from your browser. You won’t get confused to choose between manual or automated because both are available in our public cloud environment. We allow our users to test on a comprehensive list of real IOS and Android devices. You can also test your app over various network conditions like 2G, 3G, 4G or Wi-Fi. You can either configure your own browser or choose from our wide range of pre-installed browsers.

Private Cloud

This option is similar to our public cloud environment, except it comes with additional benefits of personalized security and dedicated access. Here, we would provide you a host of devices in our enterprise grade data center and you can choose your own device. If you have a geographically distributed team, then they will have secured devices over a browser. We make sure that your data is safe on our platform, as we allow only authorized team members to access.

On-premise cloud

In this option, we provide you with the necessary hardware and give you the freedom to set up your own secure device lab. You will have complete control of your own on-premise lab.

In addition to have exactly the same features of our public cloud, on-premise model contains supplementary benefits. On-premise cloud gives you the freedom of plug-in with your existing set of devices and provides you access to a geographically distributed team. Manual and automated- both the testing techniques can be used and with a simple plug-in, you can access it from any rack. Also, there is no limit for the number of devices which can be linked!

At the end of the day, the developer has to choose the best platform for his app. But choosing the right one saves so much of hassles.

Avinash Tiwari | Posted on March 7, 2016September 5, 2022 | 2 min Read

Why it is Important to Test Your Mobile App on Different Devices?

Test Your Mobile App on Different Devices

The Technology involved in mobile devices is changing rapidly. Mobile phones have literally personalized the choices in our lives, experts forecast that the future devices will be the remote controls of our lives. The services or functions are run by apps in specified platforms. And each platform has its own set of parameters to run an app. Mobile phone or device manufacturers are going through a breathtaking pace of change over the years and keeps on innovating new ways of doing things!

Why Apps fail?

Above data clearly show that handling Device fragmentation is one of the biggest challenges for App developers. Android has more fragmentation issue compared to iOS. Because the number of mobile vendors, is comparatively higher. However, even iOS faces certain amount of fragmentation issue. As there are different software versions and devices. And different devices run different iOS versions.

Mobile browsers can be challenging too! There are end numbers of browsers like Safari, Opera, Goggle Chrome and Dolphin. And each one of them has different versions for different platforms!

“So, what’s the right choice? Buying every device available in the market?”

Not necessarily, right device matrix is the key to success.

You can choose one of the two approaches to arrive at your device matrix

Device diversity Approach

Decide the device matrix based on key parameters like OS versions, screen size/resolution, manufacturer/device family (Android), operator, CPU, and input method
Objective is to maximize the variety of devices

Market segment + Device popularity approach

Choose devices with the highest market share
Objective is to maximize market coverage

Once you have the right device matrix, Device Cloud is the best option to get quick access to your device matrix.

As a tester, you must consider the ever increasing number of physical devices. The most important implementations should be automation, quality assurance, security and device compatibility. Also, ensure that the software scripts cover the core functionality of the application, so that it can run across all the platforms.

Test Automation

Test Infrastructure

Test Management