2 min read

Transition to Open Source Test Automation

Transition to Open Source Test Automation

The transition from an old test automation framework to a new implementation can be a real challenge. Nikolaus Rieder, Test Automation Engineer at Schrack Seconet AG, has gone through this process and gained valuable experience in the process. Through patience, strategic planning and an open eye for external resources, he was able to leave manual adjustments and copy-paste work behind and introduce the Robot Framework. This modernization has significantly increased the efficiency of test automation and shows how important it is to update old systems and use external solutions to make progress.

“And then, unfortunately, the thing (framework) simply grew too quickly, which probably led to this monolithic structure. (…) And little by little, layer after layer was added until the whole thing was just a Jenga tower” - Nikolaus Rieder

Nikolaus Rieder has over 7 years of experience in quality assurance, specializing in test automation and manual system testing. After starting out in technical field service and support, he focused on the automation of test processes. He is currently researching machine learning models for UI test support in his bachelor thesis.

Highlights of this episode:

  • Nikolaus Rieder works as a Test Automation Engineer at Schrack Seconet AG and deals with fire alarm systems and communication systems
  • The old automation was semi-automatic and required a lot of manual work
  • Nikolaus decided to replace the old framework and came across the Robot Framework as a solution
  • The transition to the new framework took almost a whole year
  • The new framework enabled more efficient testing and improved reporting
  • Nikolaus learned to be patient and stay calm during the lengthy conversion process
  • He plans to open-source the remote library interface to help the .NET Core community

Further links:

From monolith to efficiency: A journey through the transition to open source test automation

The transition to open source test automation can be a challenge, but with the right strategy and perseverance, it is possible to move from an old, monolithic system to a more efficient and powerful framework. Nikolaus Rieder shares his experiences and learnings from this process.

A monolith stands in the way

Nikolaus’ journey began with an automated system that was in reality only semi-automated. Human intervention was always required to run tests and interpret results. The complexity of the old system, which had evolved over the years into a veritable ‘Jenga tower’, made it almost impossible to work efficiently. The realization that change was inevitable finally led to the decision to take a new path.

The switch to open source

After careful consideration and numerous discussions within his team, Nikolaus decided to take the bold step of completely replacing the old system. The Robot Framework was chosen as the central component of this new era of test automation. This step required not only technical skill and a thorough evaluation of various tools, but also a strong will and persuasion within the team.

Challenges and solutions along the way

The changeover was anything but easy. In addition to the technical refactoring, Nikolaus also had to deal with resistance to change while ensuring that daily business could continue. By using a manual test team during the transition and managing resources and time wisely, a smooth transition to the new system was ultimately achieved.

The success of the new: more than just an improvement

The new framework not only brought about a significant improvement in the efficiency of test automation, but also enabled better integration into existing development processes. A direct comparison of the old and new systems clearly showed the advantages: Fewer lines of code for individual test scenarios, faster turnaround times and an integrated reporting system quickly became the new standard.

Personal learnings and outlook

Looking back on this transformative journey, Nikolaus emphasizes the importance of patience and a positive attitude towards change. The process has not only helped to improve the testing processes at Schrack Seconet AG, but has also allowed Nikolaus to grow personally. He now even plans to share his learnings and enrich the open source community by providing his solutions.

Test Automation of Mobile Apps

Test Automation of Mobile Apps

Sometimes the first attempt at test automation fails. But in addition to the frustration and the need to explain to management, failure always brings...

Weiterlesen
Will AI replace the test engineer?

Will AI replace the test engineer?

Rudi is an accomplished Agile and testing expert and takes us on his remarkable journey from carpenter to tester. He also talks about the skills and...

Weiterlesen
Test automation with Selenium

Test automation with Selenium

Boris Wrubelis a test automation specialist. In the interview, we talked about the automation framework Selenium. Based on his project experience,...

Weiterlesen