| • Cmcmahon | |
| Sep 2 2014, 6:08 PM |
| F107208: messages_notification.jpg | |
| Mar 30 2015, 11:42 PM |
| F107206: alerts_notification.jpg | |
| Mar 30 2015, 11:42 PM |
| F14657: Screen_Shot_2014-09-02_at_11.05.05_AM.png | |
| Nov 22 2014, 3:41 AM |
User with messages in Echo flyout should have a "Mark all as read" button, but does not. See screen shot.
This is the browser test failure at
https://integration.wikimedia.org/ci/job/browsertests-Echo-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/34/
Version: unspecified
Severity: normal
See also:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | zeljkofilipin | T94150 Fix scenarios that fail at en.wikipedia.beta.wmflabs.org or do not run them daily | |||
| Resolved | None | T72298 C9. "Mark all as read" button can't be found by browser tests |
Jon, Bug 70329 - "Message notifications not working" - doesn't sound like this bug, so I'm un-dupe-ing.
I am seeing "Mark all as read" on ee-flow and beta labs when I have notifications from Flow in the Messages pane. Looking at the attached screenshot, Messages(0) means you have zero unread message notifications and they all look gray, so there is indeed no "Mark all as read".
(The old way "Mark as read" worked is if you had more alerts than the non-scrolling flyout could show, "Mark all as read" would mark all the notifications as read, not just the ones appearing in the flyout.)
This is failing for another reason - the default tab was changed and the test was not updated - there needs to be a new step "And I switch to the messages tab"
Change 159685 had a related patch set uploaded by Spage:
QA: update Echo messages test
Change 159685 abandoned by Cmcmahon:
QA: update Echo messages test
Reason:
overtaken by history: https://gerrit.wikimedia.org/r/#/c/160477/
Reopening for regression bug, the "Mark all as read" button is missing again in beta labs, although it functions normally in test2wiki right now.
At a quick glance, it seems the
"And I have a Flow message that triggers an alert notification"
isn't happening. The Echo notification badge count doesn't go to 2, there's no recent message in the messages tab.
For that matter, there's no recent alert in the alerts tab. Alerts are marked on view, but I would expect to see something more recent in there than "1 day ago"
It might be delayed notifications: to check see if 'Selenium user firefox' has more recent messages.
I'm not getting any Flow Notifications at beta.wmflabs. I replied to myself and thanked myself (via a testaccount) at http://en.wikipedia.beta.wmflabs.org/wiki/Topic:S3bmb9jyd5l7c34i - I got the Thank notification instantly, but the Flow-reply notifications have not shown up after 1 hour.
This is still an issue. If you don't care about the browser tests you should probably disable them... (but I highly encourage you to rethink this if it is the case)
I've flagged this to be estimated; we should definitely highly consider it for our next sprint.
Where are you missing the "mark all as read" link? I can see it, on both mediawiki and enwiki.
Note that it doesn't appear on the Alerts tab, and does appear on the Messages tab.
Here's screenshots I just took from enwiki.
The recent build https://integration.wikimedia.org/ci/view/BrowserTests/view/Echo+Flow/job/browsertests-Echo-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/528/ is green.
The scenario Scenario: Mark all as unread # features/messages.feature:4 is present and seems to be passing.
What was checked:
