We are running the WikibaseLexeme's selenium nodejs browser tests against beta every day and they currently fail every day.
This leads to an email about failing tests being sent out every day which is habitually ignored by everybody. This is not good as it leads to similar emails about newly failed tests being overlooked as well.
Try to keep the same level of functionality tested as before but make the tests reliable and green.
If the issue turns out to be significantly complex (e.g. because of the issues in the testing infrastructure), the task should probably be tackled using different approach (make it a subject of a dedicated "project" - hike in WMDE vocabulary).
- Functionality covered by existing tests is still covered
- Tests are running and green (not just disabled)
- Jenkins UI can be used to trigger "rebuilds" of the daily jobs at any time for faster iterations
- given the same browser test suite is run on per-patch CI jobs for WikibaseLExeme extension, it is assumed the issues are (mostly) on the test infrastructure side