Letter from the Editor

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.

As software development has changed so dramatically in the past decade — from same sprint Test Automation in agile, to Selenium as a universal browser test tool, to service testing using containers in DevOps — so has Test Automation.

But at the same time I am noticing a new trend that has not been as obvious, or as striking in the past. It’s the phenomenon of the ‘have’ and ‘have nots’! That is, those who have significant Test Automation programs and those who do not.

Some organizations have become quite sophisticated in their automation, some struggle with the very basics, and most organizations are somewhere in between.

From the first survey we did in spring earlier this year, we found that there was a very large number of companies who do not have Test Automation at all. At the same time, we know that there are companies where the Test Automation software development project is nearly as sophisticated as the production code project. Tens of thousands of automated tests with sophisticated development and maintenance methods are running on hundreds of virtual machines or real devices in a state of continuous testing.

Between these extremes, there are many levels of automation. For example:

  • Small, but hopefully, effective automation, such as one automated test or smoke test suite that run against each build.
  • A few happy path workflow, or transaction tests, or full transaction tests that touch perhaps — all the outside services or major functionality and are run against each platform.
  • A small regression suite with test design and maintenance and cross platform abilities, but also with gaps, perhaps, of various services, subsystems, or devices and platforms.
  • Significant automation program, high coverage diverse platforms, significant maintenance, and manageable.
  • Sophisticated automation that scales at a high volume, with an automated process that runs on a significant amount of systems and has its own development team.

As always there are constant demands to go faster, do more with less, and automate more.

Three aspects of this situation put pressure on test automation programs:

  1. There are also universal goals to test automation, such as higher coverage and lower maintenance.
  2. That each level of automation has its own unique issues.
  3. That with Continuous Integration and Continuous Delivery in DevOps, each of these levels need to tie into the ALM tool chain and run automatically.

A critical task when optimizing your test automation suite, or beginning to build a test automation program, is recognizing the issues. This is where LogiGear Magazine can help.

I suggest that you look at the infographic “Top 10 Must-Haves for Test Automation” to help you recognize areas you can improve on in your practice.

In this issue, we take a dive into the world of API testing, a growing skill for testers in automation. But more exclusively we have a fresh cover story breaking down voice apps and the effect it has on Test Automation.

Prashant Hedge tells us everything we need to know about API testing in the Blogger of the Month spread. Lawrence Nuanez acts as our guide in “Climbing Mount Automation.” The 3rd survey results are here to help us reflect on test automation, based on the feedback from our readers.

Beware of the dangers of Test Automation in yet another exciting infographic, and don’t miss out on your chance to win a $100 Amazon gift card by taking our last survey in the State of Software Testing Survey Series — this one is on “Modern Distributed Test Teams.”

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

“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 ...
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.
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. ...
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 ...
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 ...
As part of my work, I spend a lot of time at client’s sites and talk to various software development organizations. I am beginning to see a problem arise regarding Test Automation. There is too much automation! Surprised? While there are still many teams struggling to make progress with Test Automation, many teams have been doing ...
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, ...
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 ...
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 ...
Digital Transformation and IT Modernization projects have shifted into high gear during the COVID-19 pandemic. Tough on some teams is having to do more with less and speed up projects on reduced budgets due to the resulting COVID-19 business climate. On the other hand, other companies are adding funding and pressing the schedule under the ...
Testing Embedded systems and testing the Internet of Things could each have their own issue of LogiGear magazine. But these days they are referred to presupposing knowledge of the other, so we thought it would be a good idea to tackle the two together in this issue to give a broad understanding of the landscape ...
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe