work on maintaining the test suite so it can be enabled in the PRs

We've experienced another incident of seemingly random failures in user forms, when playing the tests in Chromium.

Turns out, field-focus-lost events, that are used for instance to trigger field validations, does not fire if the Chromium browser don't have focus. This easily happens - you drag out the test terminal window from under the Chromium window to view the logs for example - and it is easy to miss, since the Chromium window will stay on top.

I posted a heads-up about this on coreteam channel.

What it looks like (on Ubuntu) when Chromium has focus - a validation event fired producing the green check-mark in 'Username'

Open

What it looks like when the terminal window has focus - the validation event not fired:

Open

See https://folio-org.atlassian.net/browse/UITEST-25#icft=UITEST-25 regarding multiple tests failing on first run on a newly provisioned black-box and then passing on second and subsequent runs.

Without having troubleshot all failures from the last couple of days, it looks like a lot of them could stem from element IDs having been removed from check-boxes in stripes-components, which again relates to a problem with duplicate IDs in certain scenarios.

See UIU-430, STRIPES-512,
and commits https://github.com/folio-org/stripes-components/commit/88e25dd05c4db98c83abd55411c82e5e0a292056, https://github.com/folio-org/stripes-components/commit/8be825faa4bf630677028e0cb107c59b23703f4a

After 7 days of passing UI regression tests there was a failure this morning: UIU-392

Been troubleshooting local test failures (things have been passing in Jenkins for some days). Mike reported having 18 failures and I had a varying number of failures on each run, suggesting more issues with the timing of re-rendering.

I added wait time in some places and all tests eventually passed on my box. We'll see if people still experience problems when running them locally.