Member-only story
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.
Recently, one comment was posted on my LinkedIn post.
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.
According to World Quality Report 2018–19, “The first time ever that `end-user satisfaction” is the top objective of quality assurance and software testing strategy”.
Clearly, and in practice, end-to-end testing is mostly not done by developers. I know some might argue, “manual testing, of course, by manual testers or business analysts, here, automation, i.e. automated test scripts”.
Hold that thought for the moment, let us be crystal clear about the fundamentals first.
- automation is an approach to End-to-End Testing.
- manual testers or business analysts who understand the objectives and the test steps, regardless of the form.
For example, a manual tester might write the below step in his test design (in a Word/Excel document).
Enter email ‘wise@tester.com’ in the user name text box on the login page.
