End-to-End Test Automation Is Judged By Results, Ongoing Results

Other factors do not matter and shouldn’t matter much, however, …

End-to-End testing for web applications involves verifying that a web app functions according to its specifications from the viewpoint of an end user. Automation refers to the practice of using automated scripts to carry out testing, without changing the inherent nature of the testing.

| Non-Medium Members, you can read this article for free on Substack.

The details in the middle, such as the:

• Programming language (C#, JavaScript, or Ruby),
• Web framework (AngularJS, React, or Ruby on Rails),
• Architecture (monolith or microservices), or
• Deployment environment (on-premise or cloud)

are not relevant! E2E test automation engineers are not concerned with these details — they are for developers to worry about. E2E test engineers focus solely on interacting with the application as an end user would.

For web applications, which are built on the W3C standard, E2E test automation choices should be completely independent of the app’s tech stack or the developers behind it.

• automation framework, e.g. QTP…