Letter from the Editor – April 2013

Automation is a mantra in testing. Anyone associated with software development wants more test automation, but it’s often misunderstood. People who do test automation know how difficult it can be. But some people do not understand that automation is code, and that it needs to have architecture and design just like production code. They do not understand that it needs code review, and especially ongoing maintenance, which can be more expensive than maintenance of the production code. These misunderstandings about automation in addition to misunderstandings about testing in general, make test automation a political problem as much as it is a software problem.

In this issue, just as with last year’s September issue, test automation is the focus. As we know, test tools have always lagged development tools. At the same time, as software development lifecycles speed up and faster testing is needed, there is an ever greater need for test automation. As the business has grown more aware of these facts, the test automation tool market has rapidly grown. Today, most ALM tools (which we’ve written about here) include test automation tools or an ability to easily integrate test automation tools as normal practice. But remember the old saying “a fool with a tool is still a fool.” Tools will not solve your test automation problems. Great test design, architecture, great data design, and knowledgeable testers along with a great tool will get you started.

One of the most profound findings from the automation section of our 2010 Global Testing Survey is that 1/3 of respondents did 100% manual regression testing. What kind of confidence will you have from that? It is difficult for product teams to fully realize what a risk this is. If they did realize, I think many more companies would make the investment in staff, training, methodology and tools to make automation as important as their production code. The risk is that high.

Test automation is more complicated today. Most test teams today have to support far more platforms than ever in addition to traditional platform combinations, additional browser combinations, matrices of client/server combinations, and now multiple mobile platforms . Supporting a large suite of automated tests is hard enough. Supporting multiple tools due to inabilities for many tools to work across platforms, browsers and especially mobile devices makes an exponential nightmare. At this point, mobile automation can be so problematic for traditional teams we devoted an issue entirely to automating tests for mobile devices in December 2012.

In this issue, Karthik KK gives recommendations for organizing your automation code; LogiGear CTO Hans Buwalda addresses misconceptions about test automation; Randall Rice shows us why automation is not automatic; Amol Kher, Wello CTO, discusses the challenges his Netflix testing team faced when implementing their mobile application; LogiGear, Halliburton and Simco collaborate on a case study to show how to leverage test automation to increase the efficiency of distributed teams; Jonathan Khol urges testing teams to use games to make testing more engaging, productive and fun; and finally, Tad Anderson reviews the book Experiences of Test Automation by Dorothy Graham and Mark Fewster.

As always, we at LogiGear Magazine hope you find useful information to help in your test efforts. Automate more!

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

In the November 2011 issue: Mobile Application Testing, I began my column with the statement, “Everything is mobile.” One year later the statement is even more true. More devices, more platforms, more diversity, more apps. It boggles the mind how fast the landscape changes. Blackberry has been kicked to the curb by cooler and slicker ...
“Why do we need to understand a bunch of test methods? I write test cases from user stories or requirements, automate what I can and execute the rest manually, and its fine.” If this is your situation: good for you. If you are time crunched, if your automated tests have lost relevance, are hard to ...
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 ...
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.
Happy New Year from LogiGear to those of us who celebrated New Years on January 1! And for our lunar calendar followers, an almost Happy New Year come February 3rd. We look forward to an exciting and full 2011 as its predecessor was a tough year for many in the software business. At LogiGear Magazine, ...
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.
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 ...
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.
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, ...
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, ...
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 ...
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?

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