Letter from the Editor – December 2015

Michael_Hackett.20150723Every 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 more with less”: do more testing, do more automation, and do it all with less staff. Then Agile/Scrum came along and we had to automate it faster. As the XP practice of continuous integration (CI) caught fire, our automation suites – smoke tests and full regression suites – got integrated into the autobuild development process, which in most cases was out of our control. Other people and tools are now running our automation and reporting back results – not by us kicking off automation when we choose to, but whenever a build takes place.

Today this process is moving at an even more extreme pace and further away from us. We see CI moving onto virtual machines and DevOps running our automation all the time (continuous testing), on all kinds of environments.

Many teams are still struggling with getting automated test into their current sprints, or Sprint +1 (getting new functionality automated, but only in the sprint following that function’s development). Some teams struggle just to get more tests automated in their development cycle at all, and end up settling for adding new automation after a release, because they just do not have the time. This is not OK. If this is your situation, you need to fix it. It may not be an easy fix, but not fixing it has a negative impact on development.

What do we have to do?

  • First, automate more and automate faster. With shorter cycles, you need automated tests, or you will never reach levels of coverage acceptable enough to have confidence in your product. Yes, automate faster.
  • You need a framework with reusable and low maintenance functions.
  • Finally, choose effective methods. We all know the idea that tests need to be low maintenance. But how do you do that? When you have a big suite of tests and some break – and not because of application bugs – how do you unbreak the test suite to run again? Simply automating step-by-step test scripts is a surefire formula for failure. Instead, choose a more sophisticated method for developing tests, like Action Based Testing.

Our tests have to be effective at validating functionality and finding bugs or breaks. And they must be efficient – suites should do this in the minimum number of tests possible.

We know that our tests are going to be run, in most cases these days, across a large matrix of configurations, browsers, devices, and appliances. In addition, now the tests will more than likely be run on a variety of build environments. It is becoming increasingly common to run the same suite of tests on a dev environment, testing environment, user acceptance or staging environment, and sometimes live/production environments. For some tools and suites, the performance demands are too great: the tool itself becomes an issue, not just the suites it runs. I myself have used some tools that develop huge problems running tests as the number of virtual machines increases. And that is only the start.

Our automation has to get better. But more automation is not always the answer. Today, the answer must be: better and faster automation. I hope this issue of our magazine gives you valuable guidance to achieve this.

We’ve also just published our 2016 editorial calendar, to give you an idea of what’s ahead for next year. As always, if you’d like to submit an article, just let us know.

All of us at LogiGear wish you a joyful and healthy holiday season and a happy new year. We look forward to continuing to provide you with great software test information in 2016!


LogiGear Corporation

LogiGear Corporation provides global solutions for software testing, and offers public and corporate software-testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast and cost-effective results. Since 1994, LogiGear has worked with hundreds of companies from the Fortune 500 to early-stage startups, creating unique solutions to exactly meet their needs. With facilities in the US and Vietnam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

For more information, contact Joe Hughes + 01 650.572.1400

LogiGear Corporation
LogiGear Corporation provides global solutions for software testing, and offers public and corporate software testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast, cost-effective results. Since 1994, LogiGear has worked with Fortune 500 companies to early-stage start-ups in, creating unique solutions to meet their clients’ needs. With facilities in the US and Viet Nam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

The Related Post

Because of the type of work I do (consulting projects at different companies), I’ve been lucky in my Software Development career to have worked on a bunch of software projects specific to hardware devices or integrating new hardware into software systems. Starting with the Palm Pilot, I worked on some operating systems (OS) projects, firmware, ...
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 ...
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 ...
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 ...
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 ...
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.
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 ...
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 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.
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 ...
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news