There are so many reasons why this isn't feasible, though. This may be ok if the tests are small, don't take a significant amount of time to run and give good feedback on failures. What happens when the well-trained developer who thought maintaining and developing 500+ E2E tests was a good idea decides to leave the business? The task of maintaining the huge test suite gets handed over to a less-than-capable Automated Tester. They do not have excellent skills in Ruby, not as much experience in Selenium or TestWise or the CICD tool.