I am building a web site using vanilla web components. Support for component testing of this tech is absent from tools like cypress and playwright. Adding such support feels like a project of its own, which will ultimately be a huge distraction from what I want to actually do. This got me thinking …

Personally I like combining/mixing UI and API testing to test integrations and workflows—using API’s and/or direct database queries to set things up for what I’m actually interested in testing via the UI, but also using the UI to check/assert on the software state after performing API actions, and v…

There was another thread here on a similar topic regarding the ROI of UI automation. There did not seem to be a single response that could clearly communicate a strong ROI for UI layer automation, even the vendors did not chip in unless they used fallacies of arguments around mythical cost or effor…

It depends also on what one want to automate, eg an API vs a Web Frontend. And AI will supposedly take the cost down to develop and maintain an automation? Personally, automation does not really rock my boat, but no Senior level programming does, thats why I became a tester in the first case. More…

All these tools focused on frontend test automation… But why? Is it because frontend devs are trying to be too clever and making UI code complex? Is it the fault of the ever-changing JS framework and SPA landscape? Why not have all the business rules, logic and complexity in the backend?

Its a common issue that a lot of UI coverage is not focused on testing the UI but on testing the many other things that tend to be better covered elsewhere in the stack. Its important to ask whether its a UI risk, that’s usually what a UI test should cover. A good way to tell is whether or not its…

We have automation for API as well as for UI running on our CI server. While the API automation covers business logic, the UI automation is meant to cover the UI itself and its integration with the server. We do not cover business logic in our UI automation. [image] andrewkelly2555: I have th…

Explorative testing is the main thing I’m looking at, to clear out a local db to various degrees then reload in the right order. Takes a while to get a new case working but the ROI is reduced tedium.

ROI part depends on the project, what parts of the project are automated, and how many man-hours have been saved with that automation, whether the tool was free or paid because some companies use tools like Katalon or test rigor, so these tools are paid and it will also impact ROI. Companies usual…

I’d be very wary of using hours saved as part of the ROI if its actual test execution hours saved. It sometimes follows the path of start by doing something wrong or highly inefficient then do it more efficiently and the ROI is based on that saving. Its a false roi on that basis, automation should…

[image] andrewkelly2555: There was another thread here on a similar topic regarding the ROI of UI automation. [image] ROI on UI E2E automation? Is it a myth? 🙋 Questions So, I’ve seen a lot of companies preach ‘we do E2E testing on the UI’ and it works. BUTTT they …

Is the ROI of automated UI testing enough?

Discussions

kristof (Kristof Van Kriekingen) 13 September 2024 07:28 11

For me, only for small sized apps which are in maintenance. Large apps that still change often and have a lot of spaghetti code are a no go

Topic		Replies	Views
ROI on UI E2E automation? Is it a myth? Discussions automation , ui-automation	25	771	23 July 2024
Which One Gives You Higher ROI: API Automation or UI Automation? Archive learning , automation , api-testing , continuous-learning	5	13839	23 June 2023
A rapidly and ever changing UI, is it worth having a UI based E2E Test? Discussions automation , process , ui-automation	27	1841	11 January 2024
What to automate? Archive automation	22	6040	20 December 2018
What issues are your automated tests finding? Discussions automation , ui-automation	3	139	26 September 2025

Is the ROI of automated UI testing enough?

Related topics