Compare two languages for automated testers, manual testers, business analysts, customers, managers, and developers.
Comparing programming languages often lead to heated debates among programmers (in different teams), with no winners. (There are no such debates among the developers within a team, as they all use the same one.)
Here I want to set a perspective. Real Test Automation is rare, even in FAANG. Check out the objective Definition of End-to-End Test Automation Success. You may be interested in this Wired article, “The Software Revolution Behind LinkedIn’s Gushing Profits”, LinkedIn “lured” one real test automation engineer to implement daily production releases. This is how rare the real test automation engineer I am talking about. Using Ruby, of course, won’t guarantee test automation success, but it will dramatically increase your chances, compared to other languages. Maybe from
Note: please note the context of this article, that is, all of a software team members, including programmers, automated testers, manual testers, business analysts, and even customers run/edit/read automated end-to-end (via UI) tests, as in a real Agile team. Specifically, the automated test count is > 50 (Level 2 of AgileWay Continuous Testing Grading) and are run daily as regression testing. With real automated end-to-end regression testing, the software is technically deployable every week or two.
Fake test automation engineers who are pretending test automation with Cypress or Playwright will disagreee. Again, this is beyond the individual tester, is about the team. To give you a perspective, I showed Visual Code and TestWise to several business…