This was discussed again today on IRC as being useful and kind of a blocker.

As for what would be useful for testing, the ideal, I think would be:

• More than 2 wikis (so, 3 at least) so we can verify that bundles work from multiple wikis and not just from 1 remote wiki.
• We'll need Flow, Thanks and Echo (of course) to be active in all of them. Flow and Thanks would be useful as base extensions to give cross-wiki notifications, but I guess they're not absolutely a must if we have other notification-producing extensions in there.
• Ideally, we should control the languages of those wikis (though I think that's a given in Vagrant?) For me, it would be awesome if one of those wikis was non-Latin and/or RTL for testing, or, at least, if we could relatively easily change its language/directionality for occasional testing.
• For browser testing, it would also be great if we could have all of the wikis initialize with "Selenium user a" and "Selenium user b" so we can test both local and remote notifications with browser tests automatically. (Though this point is probably not that urgent to have, and we can always add those manually when/if we decide to run cross-wiki proper browser tests)

At the very minimum, having 3 wikis should be enough. The above points are good extras if they don't take too much time to set up.

Also, I believe all three wikis must have some unified login (CentralAuth?) to work as cross-wiki notifications for the same user.

Change 260713 had a related patch set uploaded (by Mattflaschen):
WIP: Cross-wiki notification support

https://gerrit.wikimedia.org/r/260713

I'm changing it to French because Zero is already using Spanish.

For browser testing, it would also be great if we could have all of the wikis initialize with "Selenium user a" and "Selenium user b" so we can test both local and remote notifications with browser tests automatically. (Though this point is probably not that urgent to have, and we can always add those manually when/if we decide to run cross-wiki proper browser tests)

The existing 'Selenium user' should be available everywhere already through CentralAuth (the patch has Echo depend on CA), but doesn't work yet. I'm looking into that now.

I'll also make a couple of global Echo users, and make the existing Flow users also global.

I can't reproduce the issue I was saying with pre-defined CentralAuth users not working.

It might have been fixed by another fix I made.

There is still an issue I'm seeing with certain users showing up repeatedly on re-provision. I'll see if I can fix the issue.

Both parts are fixed now.

Change 260713 merged by jenkins-bot:
Cross-wiki notification support

https://gerrit.wikimedia.org/r/260713

Checked for cross-wiki support - Notifications are displayed in all enabled wikis:

http://fr.wiki.local.wmftest.net:8080/wiki/Accueil
http://he.wiki.local.wmftest.net:8080/wiki/%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99
http://frwiktionary.wiki.local.wmftest.net:8080/wiki/Accueil
http://zhwikivoyage.wiki.local.wmftest.net:8080/wiki/%E9%A6%96%E9%A1%B5

For example,

The image looks a bit weird to me; there should not be <tt> tags or {{FlowMention|...}} renders in the description or text.

This might be a bug in the way we do the parsing, or the way Vagrant works with the parser? Not sure if this happens in production sans-Vagrant?

As far as I can tell, this particular ticket is satisfied. @Mooeypoo , @Etonkovidova, do you need to open a separate bug for the tt tag?

Or am I misunderstanding and the tag is actually pertinent to the testing?

The only thing I want to make sure in this case is whether this is a general bug or a vagrant specific bug. If it's a Vagrant-specific bug then something potentially went wrong with implementing x-wiki in Vagrant (in which case this ticket isn't closed yet) -- but if it's happening in general, then it should be a separate bug.

Pinging @Catrope on this one. I'm not sure how things work with the parsing, and I believe new work is being implemented too due to a separate mention bug?

In T119999#2121005, @Mooeypoo wrote:

The image looks a bit weird to me; there should not be <tt> tags or {{FlowMention|...}} renders in the description or text.

It looks like those might be from a topic title. We do not parse that in topic title (deliberately, it is the same as the edit summary parser normal pages use).

@Etonkovidova is that correct (<tt> and {{FlowMention}} were your testing input into the topic title field)?

@Etonkovidova said these were topic titles.