|
Automated Testing whether on UI or otherwise should provide value to be worthwhile.
If you find yourself spending more time fixing broken tests and maintaining scripts than writing meaningful tests, then you need to change your strategy in how you automate and run your tests.
GUI Automation Testing does need more maintenance than say unit or API tests, due to the changes on the UI and locators.
So, the less tests that you have at UI layer the less of maintenance effort.
I would use the "Inversion of the test automation pyramid" principle, where you focus majority of your tests at unit layer, and if you have web services that's where you can check and test the application logic, and then just have only a handful of automated end-to-end tests on the UI. |
