Story: “What is the Most Challenging in E2E Test Automation?”

Many software testers know the answer when they think deeply. However, in practice, they often neglect it and focus on trivial matters. Therefore, test automation failures.

This is one of the Stories series.

Table of Contents:
· The Story
· This is an Important Realization but often Neglected
· The Story of S Continues (in a few year's time)

The Story

In 2016, I worked in a large tech company (over 500 IT staff, considered large in my city) as a test automation engineer (contractor). One day, the newly-joined testing director, S, who is responsible for the overall testing process in the company, invited all software testers (~70) to a meeting.

In the meeting, after the usual introduction (his and then self-intro from everyone), S asked what test automation technologies were used in different teams. There were many answers:

• Micro Focus QTP
• Selenium WebDriver
  - Java
  - Ruby
  - C#
  - JavaScript
  - Python
• SoapUI
• Watir