1. With this case study, I hope you will get an insight of what's involved in test automation and release pipeline re-structuring, which can also be used for setting up a framework and pipeline from scratch.

Peet is a seasoned software tester with almost 20 years of experience. He specialises in test automation, test management and continuous integration. He started his career in The Netherlands and later moved to Scotland. On both sides of the North Sea, he has worked on numerous projects in a wide range of industries. He currently works as a senior verification engineer at Optos in Dunfermline, Scotland. In his work he wants to be challenged and is always on the lookout for the next problem to solve. And when not working, he likes to explore the Scottish countryside and enjoys a good ale or whisky.

Having worked for the same employer for 12 years, I recently joined another company. Having come from a situation where I’ve set up a test automation framework with a release pipeline from scratch, I now arrived at a place where the plumbing was already in place. But that plumbing needed attention.

And with that, the problem I faced was to re-structure the existing automation and release pipeline without loss of output. With little or no documentation at hand, some of the questions that needed answering were:

How does it all work?
Why is it set up the way it is?
Who was/is responsible for current set up?
What can be/needs to be replaced?
As well as the technical challenges that had to be solved, there were several other hurdles to overcome. I will tell you all.