At the moment Selenium is used to test the UI. Selenium itself has some steep learning curve as one has to be familiar with programming and these tests a quite fragile especially when run in headless mode.

From a DevOps perspective it would be great if Ops and QA would maintain and extend these UI tests themselves.

How do you deal with this? Are there any tools that create stable UI test that are easily to maintain? How did you change the culture of "Oh UI tests, Dev responsibility" to "Oh UI test, fix myself and create PR"?

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.