Correct a Common Misconception: “Using the Coding Language for End-to-End Test Automation”

A common wrong choice. End-to-End Test Automation Scripts are nothing to do with code and shall be in a scripting language.

You can develop automated end-to-end tests using one script language, e.g. Ruby, for any websites, coded in various languages.

Recently, one comment was posted on my LinkedIn post.

Sadly, if the titles on his LinkedIn slogan are real, this explains why >99% end-to-end test automation failed. Too many fakes! He clearly does not understand the real meaning of White-Box and Black-Box Testing, and the meaning of “Scripts” in test scripts.

This is a common and very wrong view. This article will explain why.

Table of Contents:
· End-to-End Test Automation for the whole Team, not just Developers
· End-to-End Testing is Blackbox Testing
· My view on programming languages is unbiased
· End-to-End Test Automation, technically speaking, is talking to an Interface
· “But surely there are some benefits … ”

End-to-End Test Automation for the whole Team, not just Developers

I think every software professional understands the meaning of End-to-End test automation: verify the app as an end-user would, but using automated test scripts.