Letter from the Editor – November 2011

Everything is mobile. What else can we say? Everything. If your product or service is currently not, it will be very soon. As Apple says: “There’s an app for that.” There is an app for everything. The race for mobile apps has consumed the software development world.

I did a few projects at Palm Computing in the late 90s. Their Palm Pilot became the first commercially successful handheld computer. It was an exciting time. And still, to have so many people around the world buying these devices seemed a bit odd─why would so many people want to carry around a little computer with them? At the same time, I did a few projects at Unwired Planet (which became Openwave) as well. Openwave is historically significant in its introduction of the Mobile Internet. With its implementation of WAP (wireless application protocol) mobile phones with a browser were an odd new invention where you could have the internet on your phone─anywhere!

Now, these two work experiences seem funny themselves; it seems like ancient technology despite its introduction less than a dozen years ago! The world has truly changed. It now seems odd to not have a smart phone. But this new revolution is not only about phones. The 2010 US Census Bureau canvassing of over 300 million Americans was completed using hand held computers. It saved millions of dollars in paper, data correlation and salary costs. This success was not without problems. There were data transmission problems in rural areas and there were update and patch problems that were said to cause “dramatic dysfunction.” But still, this hand held computed was a big success, saved millions of dollars and revolutionized the census process.

With these “first of their kind devices,” testing needed new and innovative thinking. Testing devices, operating systems, applications, performance, connectivity, download speeds, security, carriers, and more, were new to most testers but very often carried out by previously skilled black box, desktop testers. The testing effort required quickly learning new technologies, trying to find tools on new platforms, and leveraging previous testing experience to rapidly test, improve quality and minimize risk. Now those same test jobs seem slow and simple. The rate of change has exponentially increased. The speed of code and product delivery has increased. Competition has significantly increased. Our test strategies and the testing itself must be more dynamic, agile, responsive, automated and effective. This will not be easy.

We want to get you started on the right path! In this issue, Gal Tunik addresses the importance of test automation in mobile applications, John Roets discusses what matters in building a test matrix for your mobile testing, Robert Binder answers questions from testers currently working on mobile projects, Blogger of the Month HarshalKharod offers a checklist for testers on what they should look for while testing and our 2010 Global Survey series continues focusing on respondents and their common challenges in testing management politics.

We will continue providing information in this budding area of testing in the near-future. We are sure to have another issue on mobile testing in 2012!

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

This is a very special issue of LogiGear Magazine. When we were putting together the Editorial Calendar for this year, we decided that instead of a technology issue, we would focus on the human side of quality and test engineering. We want to focus on individual Test Engineers and their jobs. We talked to a ...
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.
Testing tools – very important, very often overlooked, and very often where mistakes are made. First, the most common mistake people make about tools is thinking tools are only about test automation! False. Automation tools are merely one type testing tool. We will try to balance this issue between test automation tools and other test ...
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 ...
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.
Software development projects are multifaceted. There is staffing and budget work. There are communication and team dynamics. There are project and process issues from what the customer wants, when they want it, revenue projections, and production dates. As part of my work in helping people deliver software, I get involved in all aspects mentioned above. ...
In our continuing effort to be the best source of information for keeping testers and test teams current, we have another issue to explore testing in Agile development. As Agile evolves, systemic problems arise and common rough situations become apparent. We want to provide solutions. For anyone who has worked on Agile projects, especially if ...
Every year, LogiGear Magazine devotes one full issue to Test Automation. We could do more than one, and perhaps even that would not be enough. The problems around automation have become increasingly complex. And now, automation is much more integrated into the software development process. For over a decade teams have been faced with “do ...
On the whole, everyone wants to do a great job, have a better work environment, happy clients and customers, and to be employed by a company earning lots of money. All great goals! But this is not always the case. When it is not, you can suggest process improvements, better tool use, different estimating techniques, ...
Methods and strategy have been my favorite topics since I started working in testing. It’s essentially engineering problem-solving. It’s both looking for efficiency and attempting to measure effectiveness. So, how do we develop a set of practices to solve our Software Testing engineering problems?
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.
What is testing in Agile? It’s analogous to three blind men attempting to describe an elephant by the way it feels to them. Agile is difficult to define and everyone has their own perspective of what Agile is. When it comes to testing and Agile the rules are what you make them. Agile is ideas ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe