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

Continuous Testing… what is it? When we first decided to do a magazine issue dedicated to the DevOps practice of Continuous Testing, I joked with someone: “It’s about testing continuously.” And their reply was: “Yeah. What else would it be?” I was joking, but clearly the joke didn’t land. Continuous Testing is about testing continuously, ...
Testing the Software Car. As usual with the LogiGear Magazine, we are tackling a big subject. With our goal of having single-topic issues, we have the ability to grab and disseminate as much information as we can related to a current topic that is interesting and also on the frontier of Software Testing.   Some ...
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 ...
Hi everyone and welcome to our fourth edition of LogiGear Magazine. This month we finish Michael Hackett’s piece on “Agile in Testing” with part five, Tools.
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.
Test automation is a big topic. There are so many different areas to talk about: tool choice, jumpstart, cross platform, services, cloud… Each of these areas have changed so much in the recent past that they could each be worth their own magazine issue.
We launched the first ever software testing conference in Vietnam, VISTACON. It was a resounding success, with well over 200 participants and 20+ speakers from around the globe; each speaking on a wide range of cutting-edge testing topics. In this month’s magazine, we have uploaded several video recordings of event presentations – giving our readers ...
As we settle into autumn, we’re taking the time to start some new traditions. This is LogiGear magazine’s first issue on SMAC. SMAC—social, mobile, analytics and cloud. We will be doing more issues in the next few years on these topics since so much of the product world is moving to this development stack.
API testing– an old school technology gets way cool again. APIs and testing them is nothing new; the technology has been around for decades. The most basic definition of an API is an exposed function— a producer (person or company) writes a function and exposes it so that others, consumers, can use it. We copy ...
A while ago, I helped start a Software Quality Certificate Program as a part of the Software Engineering Program at the University of California, Santa Cruz Extension in Silicon Valley. I was on the Board of Advisors. While putting the curriculum together, a few people suggested a Measurement and Metrics course. Since I was teaching ...
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 ...
There is a growing software development dynamic of teams without Testers. When I first went into Software Quality, I learned one thing right away: My role was user advocate. My main job was to find bugs. This is the Lean principle called Amplified Learning. We learn about behavior by testing. Even then, validation was not ...

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