Test Automation in DevOps
The next evolution of test automation is Test Automation in DevOps. This is the process of executing automated tests as part of the software delivery pipeline in order to obtain continuous and rapid feedback on the business risks associated with a release candidate. It has evolved from and extends test automation to address the increased complexity and pace of modern application development and delivery.
Why you should care
The speed and quality of software delivery is now critical to winning business. The increasing adoption of Agile and DevOps approaches also places more demand on the speed and quality of testing. You simply cannot keep up without Test Automation in DevOps.
How we can help
We will give you a few tips and share our experience how to start or improve your current test automation.The sessions are organized as 1:1 calls. Once you register, you’ll schedule your session when it suits you best.
Whom you’ll meet on call
Marcel Veselka has spent his whole career in software testing. He is currently working as a Principal Software Testing Consultant at Tesena, which he also founded in 2013. He is also former vice-president of the CaSTB (regional ISTQB board) and co-founder of testing community called [pro]Test!. His special interests are modern testing approaches, including all the trending topics such as test automation, testing in Agile and DevOps, and AI and machine learning.
Tesena, from its delivery centers in Prague, Vienna, Bratislava and Brno, is helping their customers across Europe to achieve digital business success by improving the quality of their software products and digital services.
Based on experience from various organization we believe we can help you to fill the gaps. This is typical process we follow when we are helping you to build your own Test Automation in DevOps framework.
Stage 1: Establish proper automation
The accelerator for successful test automation. We set-up your own tailored test automation framework. Leverage our pre-built components, tool knowledge and expertise. Avoid learning pains and reinventing the wheel. You’ve removed all issues you’re encountering and using a smart reporting system which can point out false negatives.
Stage 2: Start the continuum
Select limited amount of scripts and let them run repetitively at least once a day, automatically and successfully. In this stage the repetition and stability of execution in small is more important than scope you are covering. Do not worry, we will scale up soon.
Stage 3: Scaling up!
This stage will bring you up to next level. We will gain valuable and meaningful coverage. We might need to introduce new tools to reduce maintenance efforts and increase efficiency via simulators and test data generators as well as introduce new way of reporting (if it is not there yet).
Stage 4: Expand
Our ultimate goal is to get rid of any manual efforts in testing. Here we cover whatever can be automated. It always depends on context however some teams might rich level of test automation close to 90%. In this stage you will need simulation even more to reach the high percentage of coverage.
Stage 5: Speed up, profit . . . and celebrate
Stage 5 is all about moving from often and regular into continuously testing. We want even faster feedback. From immediate feedback where developers can benefit from. Continuous delivery cuts the defect fixing time.