Test Automation of Mobile Apps

After four years, the complete test automation of a mobile app was discontinued - because it produced effort instead of relieving it and let critical bugs through. Instead of patching things up, a radical restart followed: requirements catalog, proof of concept, new technology stack. The two central goals: Manual testers must be able to automate themselves, and the variety of devices must be covered - without breaking the team.

Podcast Episode: 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 a gain in knowledge. Felix and Alicia used this gain with their team and, with the help of Christoph, successfully got test automation up and running.

“Germans are very, very sensitive when it comes to insurance products. Because everyone thinks they are the best driver and assumes that they will definitely get the 30%” - Felix Doppel, Alicia Heymann, Christoph Singer

Felix Doppel started his career in 2009 as an insurance salesman, specialized in the automotive department of HUK Coburg and later turned to software development and test automation in the mobility sector, where he has been working as a test manager since 2021.

Alicia Heymann completed her training as an insurance and finance clerk in 2016 and specialized as an ISTQB-certified tester in the field of software testing for mobile apps, supporting the mobility service and the “HUK Mein Auto” app since 2022.

Christoph Singer has been working at imbus AG since 2015, where he specializes in test automation by supporting customers in the introduction and implementation of customized test automation architectures in various projects.

Highlights der Episode

• Throwing away test automation after four years is brave - but better than years of maintenance costs with no benefit.
• Requirements catalog before tool selection: What should the tool be able to do before you adapt to the tool.
• Keyword-driven can be a better fit than behavior-driven - your team has to find that out for itself.
• Test automation isolated from the team: Professionally weak, technically strong - it won’t work without QA.
• Mobile device cloud with real devices instead of simulators - this is the only place where real errors occur.

From zero to one hundred: The success story of an initially failed test automation project

Mobile app test automation: a journey from failure to successful redesign. We dive into the challenges and solutions that the team around Felix Doppel and Alicia Heymann, with the help of Christoph Singer, experienced on the way to effective test automation of our mobile app.

A courageous new beginning

It was a challenging decision, but a necessary step: the entire test automation solution for the mobile app had to be rethought from the ground up. After realizing that the original approach was causing more problems than it was solving and confidence in automation had been lost, Felix and Alicia were faced with a crucial choice. Either carry on as before or have the courage to take a completely new path. They chose the latter. They opted for a completely new start, which meant abandoning the existing solution and setting out on a new course.

The role of the agile team in test automation

Switching to a completely new approach required not only a technical rethink, but also an adjustment to our way of working. As an agile team, they took this opportunity to learn from previous mistakes and adapt the test automation process. This step allowed them to readjust their focus and ensure that the test automation solution was not only functional, but also efficient and user-friendly.

Technological and organizational challenges during implementation

The introduction of a new test automation solution presented both technological and organizational challenges. On a technical level, a solution had to be found that supported both Android and iOS platforms and covered a wide range of devices. Organizationally, the entire team - from developers to testers to product managers - had to be committed to this new approach. Through numerous workshops and close collaboration, it was ultimately possible to develop a robust and flexible test automation strategy.

The key to success: involving all team members

A key factor in the success of our new approach was the involvement of all team members in the test automation process. By enabling every team member to actively participate in the creation of test cases - regardless of their technical background - a deeper understanding of the importance of high quality testing and a stronger commitment to the overall project was fostered.

Findings from the process

Redefining the test automation of a mobile app was instructive. The team learned the importance of flexibility in the agile process, as well as the need for clear communication within the team. It also showed that a well-thought-out plan is essential for implementing test automation strategies. The biggest takeaway, however, was that the courage to start fresh and take risks can lead to innovative solutions.

What happens next?

With the successful relaunch of our test automation strategy, Felix and Alicia are now optimistic about the future. Their goal is to continue to develop innovative solutions and continuously improve our automation processes. The experiences and lessons they have learned from this process will help them to tackle further challenges with confidence and ultimately ensure the success of the product.