|
| Summary: |
NotificationsSettingsIT#watchAndRename fails locally when run after the other tests of its class |
| Issue Type: |
Bug |
| Affects Versions: |
18.6.0 |
| Assignee: |
Unassigned |
| Components: |
Development Issues only |
| Created: |
11/Oct/26 21:40 |
| Priority: |
Minor |
| Reporter: |
Vincent Massol |
| Description: |
What happens Running the whole NotificationsSettingsIT class locally, watchAndRename fails on its last assertion, which checks that the original reference of a renamed page is no longer watched:
testUtils.gotoPage(testReference);
watchButtonElement = new NotificationWatchButtonElement();
assertTrue(watchButtonElement.isNotSet());
Command used:
- The test passes when run on its own, so it depends on state left behind by the tests that run before it in the class (@Order 1 to 5).
- The failure is unrelated to XWIKI-24621, where it was found: the class gave the same failure, with the same message, both with the XWIKI-24621 fix and with the unmodified master version of NotificationsWatchUIX, two runs each. watchAndRename never opens the watch modal anyway.
- Environment: macOS, HSQLDB embedded, Jetty standalone, Firefox, on 2026-08-12 with the master of that day (18.7.0-SNAPSHOT). It has not been re-checked since then; the class has gained tests in the meantime (
XWIKI-25142, XWIKI-25113).
Not seen on CI Since 2026-06-01 the test passed 2137 times out of 2146 on ci.xwiki.org. The 9 failures all happened in builds where other tests of the class failed too, so there is no isolated failure of this test on CI, which is why this issue is not labelled flickering. Next step Not investigated yet. Since the test passes alone, start by listing the notification filter preferences of the test user (FIRST_USER_NAME) just before the last assertion, to find which one, left by an earlier test, still applies to the original reference after the rename. |
|