Back-end tests can be super robust immediately whereas front-end ones generally take some tweaking to get to that point. I still think they’re worth it, especia

Back-end tests can be super robust immediately whereas front-end ones generally take some tweaking to get to that point. I still think they’re worth it, especially for testing the core feature happy paths. Selenium and the like are fine. Being end-to-end these type of tests cast a wide net so it’s worth logging the dev tools / browser network logs if you can at the time a test fails as well as taking a screenshot. Use a cloud device service like BrowserStack and setup some CI. Who wants to test this stuff manually after the first time. Make sure the front end devs don’t change your data-* attribute tags or whatever else you’re using to find elements and are strict with that. As lead dev and co-founders at Tesults.com I’d obviously recommend you use that for consolidating test reporting from your back-end and front-end tests :-)