User Details
- User Since
- Jun 5 2025, 4:08 PM (26 w, 3 d)
- Availability
- Available
- LDAP User
- SLong
- MediaWiki User
- SLong-WMF [ Global Accounts ]
Mon, Dec 1
Wed, Nov 26
Fri, Nov 21
It is! And one of the draft hypotheses I'm considering for the next fiscal year involves creating and maintaining this as part of Quality Services' work. t's possible we could pull it in sooner, depending on other commitments.
Oct 31 2025
Makes sense, thanks. Like you mentioned, null is tricky. Glad you figured it out!
@vaughnwalters Are there automated tests to validate navigation on this? Either UI, integration or unit tests? If we can set up data appropriately for this situation in Catalyst this would be a decent opportunity to create a test automation ticket for future work to make sure it doesn't happen again
Just out of curiosity here - was the root cause that the following user had null for username? Which is acceptable data because it's a nullable column.
Oct 29 2025
FYI there's folks on Test Platform (@armeniki 's team) that can help understand options and time commitment here. Or I can! I love performance testing.
Oct 23 2025
Hey folks! I'm the Engineering Manager of the Quality Services team (formerly part of the QTE team). Kosta let me know about this ongoing discussion and I wanted to see if I could help out.
Oct 7 2025
Sep 29 2025
@ABorbaWMF Mind attaching your test plan here?
Sep 24 2025
Sep 22 2025
Sep 15 2025
Subscribing to this because it's going to be a very useful document for my team.
This is an interesting task that might be useful to pick up again and move to the Quality-Services mediawiki. Accessibility is important but not urgent, currently.
Sep 11 2025
Hey folks!
Sep 8 2025
From Native Apps: They're researching the impact this may have on Native Apps currently. @ABorbaWMF will be producing a test plan in the near future around any necessary testing based on that investigation.
@Edtadros Would you be able to put some brain power to this to determine if there are specific flows within the context of "Readers Growth" we should be specifically hitting for this potential change.
Hey folks! I was made aware of this a couple of weeks ago and will help keep things organized and reported here (since I manage the QS team). I've flagged it with them and am following up individually to ensure that as teams get on top of this we make sure to track and provide updates here.
Adding this to the tech docs team backlog so we can review and prioritize
Sep 5 2025
@Ryasmeen @EstherAmoo flagging this as it might be good to do a Root Cause Analysis on this since it escaped all the way to production and now has to be redone. An initial glance makes me wonder if we could write an automated test for it?
Sep 2 2025
Genuine question: is there a reason why the Security-Team/Tech-Docs-Team can't do this? I only ask as (I assume) these will be the teams within the WMF with the greatest domain knowledge on security/documentation-writing matters. I appreciate that teams have limited amounts of time in which to do things, but this seems like it should hopefully be a relatively minor documentation refactor for those with the relevant knowledge.
Aug 22 2025
Jul 22 2025
This can't really be started until we have a good understanding of what constitutes a "smoke test" plus what functionality will be touched by the MFA project. It only makes sense to start on this after we sync with the security team on August 11th, depending on what they say.
Jul 21 2025
Jul 17 2025
What's Tested?
Jul 15 2025
@ABorbaWMF is out sick, I'm taking a brief pass at what test should be automated as part of this work - to provide a critical user journey coverage for this specific epic.
Jul 14 2025
Jul 7 2025
Mistakenly assigned to Anthony. I'll be creating the template.
Jun 27 2025
No action needed, I'm investigating how to track work.
Jun 25 2025
Hey @pfischer mind putting this in a more appropriate backlog? I'm just trying to clean up the Quality-And-Test-Engineering one so that I can use it for Quality Services specific working utilizing the tooling.
@Aklapper Curious if we can move this ticket away from the Quality Engineering backlog - I don't see that there's action from my team on this and I'm trying to clean up that backlog in prep for incoming projects.
Not a bad idea but this is something like 8 years old now so I'm closing out the ticket.
Jun 18 2025
Jun 17 2025
Jun 12 2025
Subscribed to understand the root cause and determine if there is an opportunity for improvement to QA processes in preventing these blockers.
