A company can achieve good test automation with Java/JS/C#/Python too, but it will cost heavily. I once said to a company , "By using JS, it will cost you 10 times more with 10% chance of success, compared to Agile Test Automation Formula (Selenium + Rspec, with TestWise + BuildWise)". The tester I mentored agreeed after working with me for one day, however, the architect sabotaged.

Remember, the audience of E2E Test Automation is the whole team. If just one test automation engineer is comfortable, the whols solution is very likely to fail.

You probably saw the quotes (in my articles) from renowned experts, "E2E Test automation is extremely hard", right?

If a task is hard to get it down properly, wouldn't be sensible to copy one winning formula exactly? Given, the formula is free, and can get noticeable income in days. Instead, people are fixated only with comfortable tech stack.

Blogging, it is easy to be picked out of the context. In fact, I am more neutural than the most in terms of technology. The fact, I wrote 5 Selenium books in each it's official languages. TestWise supports Mocha(JS), PyTest(Python) and Cucumber. So is for BuildWise. I taught my daughter Playwright, and she crushed the so-called 'best test automation engineer' in a large telecom company, on her internship.

I simply states, for testing, we need verify the results (as a tester), cannot repeatly fail with poor exccuses. web changed ittle for 20 years. With every failure (and failed automation framework), the reputation of Test automation engineers goes down.

According to Patrick Copeland, "(real) test automation enginerers are gold" (same by LinkedIn chairman). We are supposed to get utmost respect, and earn maybe half-milliion US$ annual salary. Now, the reality: ruined by fakers, sadly. the most damage was done by JS testers.

Check out this article, "Test Automation and Continuous Testing Competition Week" https://medium.com/geekculture/test-automation-and-continuous-testing-competition-week-72edca4a8846