Letter from the Editor – June 2018

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.

Many organizations recognize that they have to hit the brakes and likely do an engineering project to re-architect the system before commencing.

Very different from organizations jumping on the Agile and Scrum bandwagons in name only, DevOps is more about business change, Operations/IT/deployment change, and investing in tools more so than Dev and Testing practice change. Although there is a big impact on the Dev team since many Dev teams take the lead on configuring the new pipeline tools. Dev and Testing got turned on its head with Agile. It’s more commonly the product architecture, tools, and deployment process getting turned upside down now.

Encouraging Operations/IT to get involved early in development, shifting Dev testing tasks left earlier in the cycle, and automating as many Ops tasks as possible are all foundation ideas in DevOps. Commonly talked about tools for this include Puppet, Chef, and Docker.

As much as tool and deployment changes are important, successful teams need DevOps Culture changes such as building trust, building cross-functional knowledge, and cutting out blame. This is a culture where everyone is working towards deployment.

You ask, what part of CD/DevOps do test teams need to focus on? I can say: first, understanding Continuous Testing. The distributed nature of quality ownership in CT includes much more Dev white box testing, specifically unit testing than many organizations are used to.  This is part of the shift-left practice. The theoretical result of this is that more unit testing leads to more robust functionality earlier that includes a different need for higher level testing and Test Automation. You can refer to many published works on the “Test Automation Pyramid,” where more testing is happening at the unit level than at the UI level.

Another profound development change that some organizations have a difficulty grasping—culturally— is the notion of a much smaller release than what we are accustomed to. DevOps is based on much smaller changes streamed into the production pipeline deployed in small increments to lower the risk of traditionally larger releases that most organizations do. This “small change” mindset has profound impacts, such as easy deployment, easy rollbacks when necessary, small focused Dev and Test periods, faster automation, and smaller regression suites with a minuscule focus.  All this for another foundation idea in DevOps: immediate feedback.

The much smaller, and faster regression test suites are a stumbling block for many test teams. I sympathize with this! The demand to continuously automate more persists in software development teams. In many cases, little thought was given to significant tagging, traceability, and most

importantly—retiring tests. This led to bloated and slow regression suites. Continuous Testing demands lean and mean automated suites. This is a shift in mindset that may take some time for test teams to catch up to, as it is a different style of automation. It’s lean.  But still remember to automate, automate and automate, but make it smarter and leaner! Making choices to not run all the automation, at all times is risky and difficult. Be sure to communicate and collaborate. Explain the test coverage for various regression runs.

If you are doing DevOps/Continuous Delivery/Continuous Testing, pay attention to this issue! In this issue, we gear our focus towards Testing in DevOps.  There’s an intriguing interview with Dave Farley, one of the pioneers of Continuous Delivery. Also included is an article from our partner, Sauce Labs that explores the complexity of combining Continuous Testing and DevOps. Whether you are just beginning your Continuous Delivery journey, or have already implemented a pipeline, this issue has you covered!

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 every year since 2011, we have devoted one edition of our magazine to the topic of mobile testing. In this year’s issue on mobile, we focus on testing from the point of view of the user experience. Most teams start with UI testing, and it may seem basic — until you look at the ...
As we settle into autumn, we’re taking the time to start some new traditions. This is LogiGear magazine’s first issue on SMAC. SMAC—social, mobile, analytics and cloud. We will be doing more issues in the next few years on these topics since so much of the product world is moving to this development stack.
Our plan for the December LogiGear Magazine was to have a forward-looking Trends and Challenges issue. However, whilst assembling our September issue on SMAC, we realized the momentum SMAC was gaining in the industry. We had a large amount of content on our hands from a range of excellent contributors. Thus, we decided to split ...
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 ...
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.
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 ...
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 ...
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 ...
I once consulted for a company to give a week-long course on testing and QA. It was a survey course covering a wide range of topics. I was setting up and chatting with students in the room. One man came over to me and said: “I have been testing for 6 months and I am completely ...
I have been training testers for about 15 years in universities, corporations, online, and individually – in both a training, managing and coaching capacity. So far, I have executed these various training efforts in 16 countries, under good and rough conditions – from simultaneous translation, to video broadcast to multiple sites, to group games with ...
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 ...
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 ...

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