We had a meeting today to discuss the possible outcomes and challenges the AHT team is facing here and risks associated with various paths. Scott and I communicated the challenges of not being able to test with mock data, and/or having a 'test harness' ability to populate deterministic patterns of expected user artifacts for QA or integration testing. My understanding is the AHT team now sees the potential need for mocking data, but mocking only reaches a level of QA certification that encompasses known known and not known unknown in the greater realm of functionality.
- Update the in-progress RA doc with newer info
- schedule followup meeting to discuss more specifics if questions remain (Expected)
email to trust and safety
tdlr; Got time for a meeting to talk about CU usage in regards to CU dev efforts regarding appropriateness the feasibility of audit and who would be the best person to talk with?
The Security Team is currently performing a risk assessment on future plans for AHT=>CU development and improvement. At some point in the maturity cycle CU checks are required on prod wikis. It's my understanding some of this is being done on test wiki now by staff, and that individual wiki communities may have their own sub-norms about the usage of CU.
Does anyone from Trust and Safety have a few minutes to talk this out with me to ensure that the plans building momentum are going to be tenable? I worry about increased CU traffic making the current audit procedures more expensive, and other inadvertent possibilities for violations of community norms. My sense is this can all be worked out but I wanted to get your perspective on things early.