QA and Test Automation Manager as well as mentor and trainer. Tech freak following all the newest technologies (and implementing them on his own). Fan of the Agile approach to project management and products. Actively speaking and traveling around the world, sharing knowledge and experience. Lover of cats, coffee, and traveling.
Linkedin: https://www.linkedin.com/in/paciadawid/
Prelekcja/Presentation:
TestOps w obecnej rzeczywistości
It’s 2016. I have the opportunity to debut on the big stage with the topic “Put your TestOps shoes on!”. Apart from the huge stress, I remember one more thing from the lecture – “TestOps” was a new term to almost everyone in the room. And it’s no wonder! The role of QA remains clearly defined in the area of quality – primarily about making sure that the application works according to the requirements. DevOps responsibilities are release, infrastructure, and the broadly understood “system operations”.
It’s 2025. AI everywhere. Deployments are becoming increasingly faster and much more frequent. -Ops elements are an inseparable part of the work of almost every engineer. “TestOps” even has its page on Wikipedia! And yet, a significant number of Testers still try to stay away from it – although the requirements for QAs are growing; we expect seniors and architects to be fully independent.
How to cope in a reality where creating an automation framework is not enough – it also needs to be integrated with the existing CI/CD? How to properly connect monitoring and alerting? Collect logs effectively, analyze metrics, and track the system? How to deploy selected changes to production without failure and manage these deployments? And eventually, how to not go crazy hearing terms like “containerization”, “observability”, “orchestration” or “provisioning”… All this at a time when more and more job offers for QA list these competencies as required.
In the companies I had the opportunity to work for over the past few years, QA specialists (also without experience in test automation!) not only worked closely together but took over many areas previously “reserved” for DevOps only. I will take you through the history of my experience in work, building teams, and taking over and implementing responsibilities that by default one would like to pass on to “those guys from Ops”.
It’s time to talk about TestOps a decade later and take care of the quality of processes!
Język prezentacji/Language: EN/PL
Czego uczestnicy nauczą się z Twojego wystąpienia? / Key takeaways:
- Understanding what TestOps truly is and what its responsibilities are
- Identifying the key competencies in this area and how to effectively acquire them
- Realizing that maintaining the quality of processes (Ops) can be just as valuable (and sometimes even more so) as the quality of the product