A Story of ~Unit, a Failed Developer-Created E2E Automation Framework I Witnessed

One downside of end-to-end test automation is that if it starts on the wrong path, it can be very difficult to get back on the right track due to human factors.

Zhimin Zhan
6 min readMay 30, 2024

--

Image credit: https://pixabay.com/vectors/slip-wet-floor-sign-slippery-6923608/

This article is one of the Stories series.

In 2019, I worked as a test automation engineer (contractor) at a finance company. Before I joined, I heard one test automation lead talking in a meetup about how well the test automation was implemented in this company.

However, after started working at the company, I could not see a sign of test automation. Over half of my team members were manual testers, with a similar ratio in adjacent teams. A few days later, I heard there was a separate test automation team in the company (on a different floor), and I talked to one senior there. They were using Micro Focus UFT (record-n-playback) and never did anything with our division. But they helped me get a UFT license (quite expensive); I tried it, but it was still bad, as a few years ago.

The application under test (AUT) is not a real web app. Rather, it is a Windows app that runs in IE (a bit like the old TestDirector). Anyway, I managed to develop a test automation solution…

--

--

Zhimin Zhan

Test automation & CT coach, author, speaker and award-winning software developer. Help teams succeed with Agile/DevOps by implementing real Continuous Testing.