E2E Test Automation Anti-Pattern: Developer-Focused Approach. Part 2: Scripting Language, Frameworks and Tools

Choosing the wrong scripting language, framework, and tools is common.

This is an article in the E2E Test Automation Anti-Pattern series.

• 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

Continuing from Part 1: It is Black-Box Testing! I will explain how a wrong Developer-Focused Approach often leads to bad technical choices, such as scripting language, framework and tools.

Scripting Language

One clear sign of developers’ influence on end-to-end test automation is the test scripts’ language. Typically, Using the Coding Language for End-to-End Test Automation, which is often decided for the wrong reasons.

For End-to-End Testing (black-box), the test script language is 100% independent from the code!