E2E Test Automation Anti-Pattern: Developer-Focused Approach. Part 4: Hard to Steer Away even after it is Proved Wrong.

I have witnessed many failed test automation led by principal/senior software engineers or architects. Few admitted to the mistakes and acknowledged that they didn’t have knowledge of E2E test automation.

Part 1: It is Black-Box Testing!
Part 2: Scripting Language, Frameworks and Tools
Part 3: Most developers Lack Proficiency in Test Automation
Part 4: Hard to Steer Away even after it is Proved Wrong

This article will discuss the human factors when software developers dominate an End-to-end Test Automation approach.

Table of Contents
∘ 1. Software Developers’ Ego.
∘ 2. Software developers generally perceive software testing (whether manual or automated) as a lesser position.
∘ 3. Software Developers tend to have a “Get it work, then done” mindset.
∘ 4. Senior Software Developers have mixed feelings about successful E2E Test Automation.
∘ 5. End-to-end Test Automation is often seen as a “Nice to Have”, not as mandatory. There is always manual testing.
∘ 6. Comprismed as taking bribes from automation tool vendors
· Examples: