Problem/Motivation
Moving to selenium has exposed a problem with the statusMessageExists() assertion. It does not wait - if the message is added by ajax there's no guarantee the message is there yet. See https://git.drupalcode.org/project/drupal/-/jobs/2218322
Steps to reproduce
See https://git.drupalcode.org/project/drupal/-/jobs/2218322
Proposed resolution
I think this method should do a wait if used in a JS test.
Remaining tasks
User interface changes
None
Introduced terminology
N/a
API changes
None
Data model changes
None
Release notes snippet
None
Issue fork drupal-3463594
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
alexpottComment #4
catchLooks good.
Comment #5
alexpottCan this be backport all the way to 10.x - there's no harm and it'll help backporting the W3C issue.
Comment #6
catchYeah I think we could go back to 10.3.x with this, just method overrides to fix a bug.
Comment #11
catchGoing to go ahead here to stabilise core test runs even though I RTBCed it.
Committed/pushed to 11.x and cherry-picked back through to 10.3.x, thanks!