2025-02-13 –, RoboCon
Our project was migrated to the cloud and relied on Robot Framework with EggPlant keywords for test automation. Robot Framework saved us by enabling the replacement of EggPlant with PlatynUI without the need to rewrite test cases. This talk will cover our practical transition to an almost seamless continuation of automated testing.
Introduction:
Our project aimed to modernize legacy software systems by migrating them to the cloud. We utilized Robot Framework with EggPlant for our automated testing needs. While this combination provided a robust foundation, it introduced several significant challenges:
- High Costs: EggPlant's licensing fees and maintenance expenses were substantial, impacting our budget.
- Complexity: EggPlant's scripting language was difficult to learn, resulting in a steep learning curve for new team members.
- Maintenance Burden: Frequent GUI changes required extensive updates to EggPlant scripts, increasing maintenance efforts.
- Licensing Issues: Problems with the EggPlant license server hindered parallel test execution, causing delays.
- Incompatibility with our Cloud Migration: Migrating our software to the cloud rendered EggPlant unusable due to technical incompatibilities and inaccessible license servers.
Robot Framework to the Rescue with PlatynUI:
Facing these obstacles, Robot Framework's flexibility became our solution. Its keyword-driven testing approach allowed us to separate test logic from the underlying tools, enabling us to replace EggPlant with PlatynUI, a custom UI-Test Library we developed and released as Open Source. Only by rewriting the keywords, we were able to continue our automated testing almost without modifying the test cases themselves.
Developing PlatynUI:
Existing Robot Framework libraries like FlaUI and SikuliLibrary did not meet our specific requirements for handling complex GUIs and adhering to our technical constraints. Therefore, we developed PlatynUI.
Summary:
In this talk, we’ll show how Robot Framework facilitated our smooth transition from EggPlant to PlatynUI. We’ll discuss key challenges we encountered during the migration, practical guidance on using PlatynUI effectively, and specific improvements we achieved over the EggPlant setup.
In-Person
Categorize / Tags:Management, Technology, eggPlant, PlatynUI, UI Testing
Lessons Learned:- how Robot Framework facilitated our smooth transition from EggPlant to PlatynUI
- key challenges we encountered during the migration
- practical guidance on using PlatynUI effectively
- specific improvements we achieved over the EggPlant setup
- Test engineers and QA managers seeking practical approaches to tool transitions.
- Software developers interested in desktop automation with Robot Framework.
- Professionals navigating infrastructure changes like cloud migration.
- Anyone interested in developing or adopting Open Source testing tools.
Beginner RF User, Intermediate RF User
- team lead testautomation at Deutsche Bahn DB InfraGO, project PRISMA
- lecturer for IT Security at HSB Akademie
I started my career in an office environment, then added a bit of marketing, event management, and logistics. I entered the IT world around 2017 through my business studies and work. Originally, I wanted to go into the logistics industry, but I "ended up" in IT instead. :)
I'm not upset about it, though, as IT is incredibly versatile and offers many directions for self-development. Through my current employer, imbus, I got to know the RobotFramework world, and I would be very excited to attend RoboCon, especially as a co-speaker.