Page - 33 - in The Future of Software Quality Assurance

Testing in DevOps 33 the knowledgeof this kind of testing is not present in the team? There are multiple approaches to face thisproblemdependingon thesituation in the team. As mentioned previously, DevOps doesn’t mean engineers should be superhu- mans.Engineerswillprobablylackknowledgeandskills incertainareas. Ingeneral engineers with a testing expertise will know a little of security and performance testing, because they are considered to be specialized fields. Being a T-shaped engineer in DevOps, however, is also about challenging an engineer to expand his knowledge and skills. It can be possible for an engineer to become potent in both securityand performancetesting. If you also consider that all the knowledgeof the service the teamprovides iswithin the team, teammembersshouldbeable toassist theengineersinthis.Operationsexpertisecouldhelpunderstandtheperformanceon server level.Developmentexpertisecouldhelpunderstandframeworkandmethods ofsecurity incode.Engineersshouldnotnecessarilybecomeexperts insecurityand performance testing, but they should be able to create tests which properly test the requirementsset for their service. Another approach can be to use a testing service for performance and security. End-to-end responsibility does not mean teams have to do everything themselves, but they shouldkeep control. In bigger enterpriseorganizations it is more common that teams deliver a security or performance testing service. What should be considered though is that working with these testing services can prove to be difficult to fit in the way of working of the teams. There can be different priorities between the teams, which could result in not getting the testing service at the momentyouneed to. It shouldalsobeclearwhat theexpectationsareonbothsides of the testing service. DevOps teams should deliver a clear request on what they want to have tested andshouldprovide the necessaryknowledge.On the other side it shouldbeclear forDevOps teamswhat is expectedfromthe tests. Between these two approachessome hybridapproachesare possible. Having an engineerwithsecurity/performancetestingknowledgein the teamforashortperiod of time or having security/performancetesting teams educate the DevOps teams to the requiredknowledgelevelare just two examples. Witheachapproachit isvery important forDevOps teams tounderstandthat the scopeof their testing haschanged.Theyare responsibleandshouldkeepcontrolof all kindsof testing their serviceneeds. 4 Automation DevOpswillnotworkwithoutautomation.Error-pronemanualtaskscanandshould be replaced by automation. DevOps teams require fast feedback and automation is thewaytoget this to the team. It canspeedup theexistingprocessesandmakesure the teamreceives feedbackabout theprocessassoonaspossible.Whenautomation isworking, teammemberscanfocusontaskswhichdorequirehumanintervention. Automation can play a role in the breakdown of the “Wall of Confusion.” It could be possible that Development and Operations used their own set of tools for