Wikimedia Quality and Test Engineering Team/Meetings/2020-02-12

= 2020-02-12 =

Attendance: Dom, Monte, Elena, Rummana, Zeljko, Jean-Rene, Anthony, Greg, Ed

Vacations/Important dates

 * https://office.wikimedia.org/wiki/HR_Corner/Holiday_List

Team Business
Dom's presentation notes

Context:

Most important risks:
 * What is CheckUser
 * Allows admins to find out IP and user agent of users
 * Mainly(?) used for sockpuppet investigation (by volunteers)
 * Also used by Trust&Safety for emergencies (e.g. threats of harm), where info needs to be passed to local authorities
 * Why it needs to change
 * Information not presented on same page: e.g. can only investigate one user/IP at a time, have to use external IP lookup tools
 * Even when it is on the same page, it is hard to make comparisons
 * For complex sockpuppet investigations, tool forces user to have lots of tabs open and to organise the data themselves (e.g. in an external tool like a spreadsheet) or have a good memory :)
 * Is the correct information displayed?
 * Is the UX improved?
 * How well is the data displayed?
 * Is all the data a user might need displayed?
 * Is it easy to make comparisons/connections between users/IPs?
 * T&S sometimes have to use in less-than-ideal circumstances (e.g. on the road, on a mobile)
 * Likely testing activites:
 * High-volume checking of accuracy
 * Using the existing CheckUser DB tables (which we are not changing) as reference
 * UX testing
 * CheckUser admins are already usability testing the current mocks
 * Not sure about plans for beta testing stages
 * Simulate complex sockpuppet investigations
 * Using specially crafted test data
 * Not sure how to generate this yet
 * Perhaps this could be based on historic sockpuppet investigations; do I draw the same conclusions?
 * ET: +1
 * Or using real data from production
 * If we are allowed...
 * Not sure how to evaluate this yet
 * Compare to mocks and acceptance criteria
 * Mocks have been designed and reviewed by domain experts
 * Compare it side-by-side with current CheckUser
 * I can do this on the same wiki with the same data; make direct comparisons
 * Compare to what information I might need ideally
 * Perhaps export data to external tool (if I am allowed...)
 * Share my conclusions with domain experts; do they agree?
 * Test that it is always possible to find out IP of user on a Mobile device
 * Few other bits of functionality
 * Not covering specifically:
 * Performance
 * Note: assumption is that this is being tested by someone else.
 * Security
 * Note: assumption is that this is being tested by someone else.

Discussion Notes:
 * JR: Are there any unknowns? Outside of how to do the data validation, not that he can think of.
 * Elena: Is the ip data being pulled from RecentChanges table? Dom: Understanding is that CheckUser has it's own tables.
 * Zeljko: The project's still in early phase correct? What's the current implementation?  Is there current CheckUser implementation being tested locally right now?  Dom:Yes Currently using the vagrant.  Currently only automation Dom's thinking about is for data acquisition and verification.
 * Rummana: Do you know how you are going to decide on test coverage across different mobile devices/different mobile browsers. Since you mentioned you will need to ensure that some things work on low end mobile devices as well. (T&S trying to find user IP from a mobile device) Dom: Not at this point.  Could ask T&S.
 * Zeljko: Figuring out how we determine whether the UX improvements have been accomplished.
 * JR: How do we solicit feedback from team? At this point it's been mostly via specific questions vs providing the whole strategy.
 * JR: Are there any other contraints that have influence the decisions about what and how to test? Not really, although things are still in flux and communication with team about implementation and design has been lagging a bit.
 * Zeljko: Was this useful for you and would you do it again.  Yes, it's valable to get this feedback.

Outgoing this week

 * Blocked by:
 * __
 * Blocking:
 * Updates:
 * Updates:


 * Test Engineering
 * Quality Engineering
 * Code Health

Callouts

 * Quality and Test Engineering

Anthony

 * What I've got going on
 * What I need help with
 * What I'm blocked on
 * Other?
 * What I'm blocked on
 * Other?
 * Other?

Dom

 * What I've got going on


 * What I need help with


 * What I'm blocked on
 * Other?
 * Other?

Edward

 * What I've got going on
 * What I need help with
 * What I'm blocked on
 * Other?
 * What I'm blocked on
 * Other?
 * Other?

Elena

 * What I've got going on
 * What I need help with
 * What I'm blocked on
 * Other?
 * What I'm blocked on
 * Other?
 * Other?

Jean-Rene

 * What I've got going on
 * What I need help with
 * What I'm blocked on
 * Other?
 * What I'm blocked on
 * Other?
 * Other?

Monte

 * What I've got going on
 * What I need help with
 * What I'm blocked on
 * Other?
 * What I'm blocked on
 * Other?
 * Other?

Pita

 * What I've got going on
 * What I need help with
 * What I'm blocked on
 * Other?
 * What I'm blocked on
 * Other?
 * Other?

Rummana

 * What I need help with
 * What I'm blocked on
 * Other?
 * Other?
 * Other?

Zeljko

 * What I've got going on
 * What I need help with
 * What I'm blocked on
 * Other?
 * What I'm blocked on
 * Other?
 * Other?