when the second test in tests/selenium/specs/page.js executes, the following alert appears:
'Leave site? Changes that you made may not be saved.
this alert blocks continuation to subsequent tests. it has a Cancel and a Leave button
the current work-around for getting past this alert is calling browser.reloadSession(), but that's an expensive operation
it would be preferable to just handle that alert by programmatically choosing the Leave option rather than reloading the entire session
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| selenium: dismiss alert in more efficient manner | mediawiki/core | master | +42 -6 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T210726 Selenium framework cleanup | |||
| Open | Mhurd | T336007 selenium: handle alert in page.js rather than using the more resource intensive "browser.reloadSession()" |
Change 915838 had a related patch set uploaded (by Mhurd; author: Mhurd):
[mediawiki/core@master] selenium: dismiss alert in more efficient manner
forgot to mention i've also tested my patch in the case where only the single test i'm using it on is invoked
npx wdio /var/www/html/w/tests/selenium/wdio.conf.js --spec /var/www/html/w/tests/selenium/specs/page.js --logLevel debug --mochaOpts.grep 'should be creatable'"
it works in this single-test use case as well due to the max wait parameter's default value