What does DevOps test

DevOps - does this affect me as a tester?


Who does not know the following typical situation

The date for the next release has already been communicated, but development is still fully in the process of implementing the expected features. The planned test phase has been reduced to the absolute minimum for the third time, so that the promised release date can even be kept to some extent. You deliberately do without feedback on the quality of the software product ...

But who are the winners and losers of this approach at the end of the day?

The only winner is the project manager who delivered in time and scope and thus (probably) received his bonus. I can't think of more winners, but there are (unfortunately) many losers, e.g .:

  • The customer: Due to inadequate quality control, he has to live with various errors in the software in his daily work and is likely to have a loss of efficiency.
  • The development company: Due to the faulty software, the customer gets a bad impression of the development company and the software product and will no longer recommend it and in the worst case even speak negatively about it.
  • Operation: This has to import various "hot patches" and "bug fixes" and each time run the risk that the application will no longer function fully, which will end in further patches ...

But how could one avoid the above situation?

Using DevOps, of course.

But what does that mean in detail?

DevOps is currently on everyone's lips, and I suspect that you have already come across the word at your company. Basically, DevOps stands for Development & Operation and does not contain either “Test” or anything with “QA” in its name. This could lead to the conclusion that it has nothing to do with testing and therefore does not affect me in my role as a tester / test manager / test engineer.

But is that really the case?

DevOps is used, among other things, to try to accelerate the flow from design to development, testing and operation, without foregoing feedback about the quality through testing. This acceleration, with the aim of releasing faster and with higher quality, requires a complete rethink on the part of the testers.

In DevOps, for example, there is no longer a dedicated test phase, but testing is carried out continuously, ideally with every build. This is called Continuous Testing (CT). This continuous testing naturally also requires a high degree of automation, especially test automation.

What does that mean for me as a tester?

You have probably heard of the "testing shift-left", i.e. testing has to move closer to development. But do you also know "Testing shift-right"? Canary, chaos engineering or A / B testing must not be foreign words for the testers.

What other practices are used in DevOps so that quick feedback about the quality is possible? These and other questions were answered during my talk at the Swiss Testing Day 2018.