Continuous Testing
TRACK TALK
How Testing is Evolving in DevOps
Can we be the same testers in a DevOps organisation, as in the past? Is that enough if we know test automation, exploratory testing, and many aspects of Shift Left, or are there any new aspects, concepts, and techniques that a tester shall be aware of? Are we able to Shape testing with the current competencies, or do we need more? In this talk, Szilard would like to share his 20 years of journey in testing, process improvement, service design, and DevOps, focusing on how testing and quality assurance have evolved, and what areas a good test professional shall be aware of.
Szilard starts with a quick recap on what is DevOps, describing the wall of confusion and the DevOps collaboration to break it. Then we check the three ways of DevOps (Flow, Feedback, Learning and Experimentation), so we are able to discuss how the discussed testing techniques are helping each of these. He will introduce what testing and QA activities we can do in each step of the Plan, Code, Build, Test, Deploy, Release, Operate, Monitor stages of a development value stream. We start from the middle and Shift Left, and Shift Right, and then we shift even more to both directions, until we understand how these steps will create a continuous loop, connecting Monitoring to Planning.
What you’ll learn
From this talk you will learn how to:
Session details
A short note from Szilard on his talk
Szilard Szell
Szilard is a DevOps Transformation Lead at Eficode, specializing in all things related to Quality. Szilard has a proven track record in large-scale DevOps Transformation Programs as a Test Coach with a focus on Quality Assistance. He has experience as an assessor, trainer, facilitator, and coach. As a SAFe 6.0 SPC, he runs successful training and coaching sessions for larger companies. As a conference speaker, Szilard is ready to share his views and knowledge with Testing Fellows, drawing from 22 years of industry experience and a multitude of certificates held. Szilard is a volunteer in ISTQB.