Mobile technology is ubiquitous, and the end customer demands nothing less than perfect performance – regardless of where they use it.To ensure that we can deliver it, testing mobile technology presents unique problems, such as frequent but short usage patterns, limited screen sizes and memory, device fragmentation, and, of course, a rapid pace of innovation. DTSC mobile app testing takes on these challenges. It’s why many of the mobile industry’s top companies rely on DTSC to make sure their network service, mobile devices and mobile apps work great – and look great – from New York to Tokyo.
Being a QA Testing company and when it comes to mobile testing services, we have built our niche in testing applications that need to be supported on various devices and operating systems. We specialize specifically in testing applications on Android and iOS devices. In addition, s also test for all types of mobile applications – be it native, web or hybrid including an optimized test automation approach that accommodates a single test suite both on the mobile and non-mobile versions of the application.
Our mobile devices testing scope includes smart phones, e-readers, tablets, PDAs, notebooks as some of the major categories. With these evolving devices and underlying technology, we strive to bring in our specialized test and domain knowledge to test applications and content on devices. Our frameworks empower us to extend additional test coverage for applications built with latest mobile and web technologies including HTML 5, CSS 3. Some major categories here include:
- Testing for Banking, Financial and Insurance specific applications on smart phones covering functionality, performance, security, usabilihty
- Testing for learning content on e-readers touching upon areas such as functionality, performance, usability, accessibility, instructional design
- Testing enterprise level deployment of devices (e.g. e-readers or notebooks in large scale deployments such as governmental organizations) and associated applications primarily focusing on functionality, performance, security
- Testing common end user applications (in domains such as retail, media, gaming) on devices such as smart phones, e-readers focusing on functionality, performance, usability, accessibility
The DTSC Mobile testing approach includes plans for the following types of testing:
- Functional Testing
- API Testing – Server and Client
- Single user Application Performance Testing
- Load/Performance Testing – A separate Test Plan is being prepared for this
- Operational Readiness Testing
Mobile App Automation
Software testing has evolved in a new facet with the entry of mobile devices and is changing the landscape of the testing overall. The time to market is expected to relatively short for the Mobile applications, and they need to be tested effectively with shorter QA cycles. Some of the companies thrive on the volatile and aggressive production cycles of the Mobile Apps. A traditional QA cycle which would take 3-6 weeks is now being reduced to just a few days. If the application does not meet the quality standards end users expectations, more cycles will be spent on fixing those issues.
Mobile testing is challenging and what make it so are the seemingly endless combinations of devices, OS’s, carriers, and networks. As it is a young market, there is a deficiency of established best practices or industry standards around it. Mobile applications have become increasingly complex and to test the performance of the app on the server, device and network can be quite deluging. There are very few tools in the market to perform automation, and additionally, the automation strategy is driven by DTSC specialists who develop custom scripts/ frameworks for related business need.
Traditional manual testing cannot feasibly cover all of the combinations, particularly when the development to market life cycle is reduced. There has to be some mechanism to test an app quickly and effectively, without wasting cycles. As a result, mobile automation has become a popular choice in overcoming the challenges in traditional mobile testing in order to maintain coverage.
Automation Approach (What/ When/ How)
What to Automate
Stable regression test set can easily be automated to ensure that basic functionality is maintained from the previous release. OS specific test cases can be defined and that case can be executed in multiple environments for that OS. Automation works best with features that are stable and are not undergoing changes. Not all features can be automated and require manual testing. The industry standards are to automate ~80% but in all actuality, ~70% automation can be achieved leading to a balance between manual and automated testing.
When to Automate
Automating very early in the applications development lifecycle might require too many changes in future and can significantly raise automation costs and effort. Only after manual testing has established with repeatable processes and stable test cases, should automation be considered.
How to Automate
There are many automation tools in the market which provide the automation engine through a public or a private cloud platform. Some very well-known automation tools are Perfecto Mobile, Device Anywhere/Keynote, ZapFix, Eggplant, Selenium, Robotium and Jamo. Here’s a list of automation tools that can be used for depending on the platform. Note: This is a basic list, and new tools get added frequently.