Letter from the Editor – September 2013

As fast as Mobile is growing, the platform is still immature and is evolving at a very rapid pace.

While there are whole countries that have migrated large government services to mobile, countries ranging from Estonia to Turkey to Kenya have many longtime mobile users have yet to use mPay or other mobile payment systems. Users are still maturing in their trust, reliance and comfort managing their lives on mobile devices. 

Mobile development companies continue to advance in supported platforms, cross platform development, greater sensor use and test automation. Yet many companies still lag in security, usability and performance testing. Mobile test strategies need to mature.

The maturing of test strategies is not only a response to development and device changes – users are more demanding and critical. Criticism in social media is rapid and damning. Bad reviews spread like wildfire and go viral before a company may have a chance to remediate a problem. Usability and performance are common criticisms and these quality aspects are commonly under tested.

The platform is evolving. New sensors from gesture barcode scanners to fingerprint scanners and more NFC (near field communication) are becoming commonplace. New integration with backend systems and data are making mobile systems more complex than the much better understood client/server systems. Most client systems to not have such great variation in screen size and resolution, do not have connection problems of dropping in and out of range, have easier update and patching control, do not use sensors for location, light, environment, IR, Bluetooth, NFC or swipe for data entry! The mobile platforms are complex and getting even more so.

How can test teams respond to these maturity problems? Problems between emulators and real devices, access to devices, test automation- especially cross-platform automation, usability, user testing, security and performance testing issues or roadblocks need to be resolved for very rapid deployment.

In this issue: Virtual City provides a list of steps to identify weaknesses in your new app; LogiGear’s John Kane reveals how to maximize mobile test automation efficient; Tania Lang argues that the traditional testing standards must be applied to mobile; Tatyana Mahlaeva reminds us that QA is necessary in all stages of mobile development, and the HowAboutWe team warns that even in large organizations, mobile development is behind in up-to-date testing practices.

This is our 3rd issue devoted only to mobile testing:

Mobile Testing – November, 2011

Mobile Test Automation – December, 2012

Our next issue is on another fast growing technology topic and its impact on testing: Cloud and SAAS (Software-as-a-service) Testing. I can’t wait.

Michael Hackett
Michael is a co-founder of LogiGear Corporation, and has over two decades of experience in software engineering in banking, securities, healthcare and consumer electronics. Michael is a Certified Scrum Master and has co-authored two books on software testing. Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems (Wiley, 2nd ed. 2003), and Global Software Test Automation (Happy About Publishing, 2006). He is a founding member of the Board of Advisors at the University of California Berkeley Extension and has taught for the Certificate in Software Quality Engineering and Management at the University of California Santa Cruz Extension. As a member of IEEE, his training courses have brought Silicon Valley testing expertise to over 16 countries. Michael holds a Bachelor of Science in Engineering from Carnegie Mellon University.

The Related Post

Every organization goes through times when the internal, or home team, cannot execute the testing project easily or quickly enough. The reasons are many, from the lack of an effective test strategy to low automation engineering skill, to staff positions going unfilled due to a great job market. With everyone working and very few people ...
DevOps can be a big scary thing. Culture change, constant collaboration— whatever that means— a big new set of tools… it’s a lot. What most teams want is to have a smooth running software development pipeline. I have stopped using the phrase “DevOps,” and now I say “Continuous Delivery.” There are many reasons for this.
How do you test software? How do you validate it? How do you find bugs? These are all good questions anyone on your project team or anyone responsible for customers may ask you. Can you articulate your test strategy─not your test process, but explain your approach to testing? I find that this can be a ...
This is our third issue concerning topics of Continuous Delivery (CD) and DevOps with the inclusion of Continuous Testing. DevOps has been around for a while and I hope the period of buzz is over and companies moving towards building a development pipeline have begun their process, including changing their test strategies.
I have been training testers for about 15 years in universities, corporations, online, and individually – in both a training, managing and coaching capacity. So far, I have executed these various training efforts in 16 countries, under good and rough conditions – from simultaneous translation, to video broadcast to multiple sites, to group games with ...
Big and complex testing. What do these terms conjure up in your mind? When we added this topic to the editorial calendar, I had the notion that we might illustrate some large or complex systems and explore some of the test and quality challenges they present. We might have an article on: building and testing ...
A lot has changed since I began staffing test projects. From hiring college students and interns for summer testing programs, to building networks of offshore teams around the world, and from having 24-hour work schedules to having instant crowdsourced public beta or bug bounty testing—things have changed.
I was just recently at a company that had a beautiful test architecture, framework, and Cucumber with tons of well-automated tests. But there was no good test management on top of the Cucumber tests, and they did not do a good job tagging the tests. Although almost everybody on the team could write and maintain ...
This is our first Trends issue in our 10- year history. Trends are important to help foresee what is on the horizon and coming next.
Change is constant. What’s different today is the rate of change. Moore’s law resulted from the observation that that the rate of change in computing power is exponential. The products, services and software landscape appears just as dynamic. At the same time, we pretty much take for granted the ubiquitous presence of software running our ...
I once consulted for a company to give a week-long course on testing and QA. It was a survey course covering a wide range of topics. I was setting up and chatting with students in the room. One man came over to me and said: “I have been testing for 6 months and I am completely ...
If you are reading this issue, you are probably aware of the impact on the business world of cloud computing. Most people do not have a good grasp on what the cloud is or how people and products can use it. BTW, you are already a cloud user. If your email is stored somewhere “on ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe