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

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?
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, ...
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.
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, ...
There has been a tectonic shift in software development tools in just the past few years. Agile practices and increasingly distributed teams have been significant factors but, in my opinion, the main reason is a new and more intense focus on tools for testing driven by more complex software and shorter development cycles. There have ...
Testers need to learn their craft and hone in on their skill set. That means building skills, sharpening their tools, and becoming creative detectives. There is no cookie-cutter tester and no best practice. The best circumstance is a fully-skilled, aggressive tester mixed with curiosity, nimbleness, and agility.
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.
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 ...
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 ...
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 ...
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 ...

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