Letter from the Editor – June 2016

Michael_Hackett.20150723This is LogiGear magazine’s first issue on the big world of DevOps. DevOps is a very large topic.

Just when you thought you were safe from more process improvement for a while—not so fast. There’s DevOps, Continuous Testing, Continuous Delivery and Continuous Deployment. In this issue, we are focusing on Continuous Testing, the part most concerning Test teams.

DevOps is, by one description, Agile for Ops. With closer input and collaboration from the business side, development and operations are using great tools to help Ops be more Agile and migrate code to production faster. But this can be complicated.

Now, I am running into organizations that say they do DevOps or are moving to DevOps but have very little in place to do so, or worse, have no idea what they are doing. This reminds me of a few companies that I knew in the Agile era, that said they were Agile, but weren’t.

I saw firsthand, how many teams limped into Agile then raced to get testing done, while working from significantly less documentation, sometimes marginal collaboration, and were still expected to get high automation coverage; some of them are still trying to get their footing. Without the culture change, empowerment, skills and tools to make it happen, a team that attempts DevOps is headed for disaster. DevOps will highlight the shortcomings of a team on a larger scale, and faster than Agile ever could.

DevOps is a minefield! To do anything here, you have to know what you are talking about. It’s not just buzzwords. Just because you began using Puppet and Docker doesn’t mean you’re ready for Continuous Deployment.

We are at the stage in DevOps, and I am greatly reminded of the early stages of Agile, where the use of a single tool or single change had uninformed people make assumptions about an entire paradigm shift. And I’m sad to see this trend continuing.

If, a dozen years ago, you dropped phased quarterly releases to sets of 2 weeks sprints with user stories instead of requirements and your Dev team started using Jenkins. That, by itself, did not make you Agile. It was a start. If, for example, the team did not have access to the business side/Product Owner daily, while significantly boosting collaboration with early team involvement and significant automation coverage—then that team would be Scrumbutt, or Agile Falls, but still not truly Agile and instead of productivity gains many teams felt more pressure and uncertainty.

It took most organizations years to implement, figure out and tune the new practices. We even already have a few anti-names—DevFlops and DevOops. But let’s not go there. Let’s do it right! There is great progress to be made here. DevOps, like Agile, is about culture. In DevOps, the whole organization focuses on the business constraints and needs rather than the whole organization working according to development or Operations schedules. Product functionality and cycles are delivered when the business needs it rather than being at the mercy of development and/or IT/Ops.

DevOps is also more about business change and Operations/IT change than Dev and Testing change. Dev and Testing got turned on our heads with Agile. This time it’s other groups getting turned upside down. Getting Operations involved, shifting their tasks left, earlier in the cycle, and automating as many Ops tasks as possible with tools like Puppet, or Chef, and Docker, among many, many others.

To get all this business driven product delivered on their schedule, there is even more use of task automation. To get a good idea of where DevOps is going—everything that can be automated, has to be. From builds using Continuous Integration and test automation we became Agile. Test teams have been dealing with these tasks for a long time, but now more tasks, primarily Ops tasks: building and maintaining environments, build promotion, provisioning, monitoring—are all becoming automated.

For Test teams, this means a lot. Apart from the team dynamics, tools, and responsiveness to change, this of course, means bigger and more intelligent test automation. How we look at test automation has to evolve and grow. Its use, as well as when, and where to use test automation and how this cycle impacts our regular Dev sprints is expanding the role of the test teams—Clearly, we have a lot to learn and a lot to change.

To be DevOps and not DevFlops—first we have to know what we are aiming for, why, goals and how we can best support the business. It’s a challenge.

I hope we can help you.

In this issue, we feature a two part series by Sanjeev Sharma, Understanding DevOps, and Adopting DevOps. Alister Scott discusses Testing in Production in our Blogger of the Month feature. Sanjay Zalavadia writes about best practices to create a test-driven development environment and Tim Hinds discusses Where QA Fits into DevOps. Steve Ropa also has reviewed the 7 Best DevOps books, and we have an interview with Skytap’s Sumit Mehrotra. I’m pleased to announce that in addition to continuing our new TA Corner series, we also have another new column, Leader’s Pulse, which largely features recommendations on how to manage Test teams.

 

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

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 ...
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 ...
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 ...
“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 ...
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 ...
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 ...
We launched the first ever software testing conference in Vietnam, VISTACON. It was a resounding success, with well over 200 participants and 20+ speakers from around the globe; each speaking on a wide range of cutting-edge testing topics. In this month’s magazine, we have uploaded several video recordings of event presentations – giving our readers ...
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. ...
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, ...
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 ...
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe