This task is about inspecting a sample of Reply Tool diffs to ensure there are no instances of content corruption.
Because "Issue 2" cannot be easily reproduced in a testing environment, it will be difficult for us to know the extent to which this issue persists prior to the patch intended to resolve it [i] being deployed. As such, once the patch [i] is deployed, we will inspect a sample of Reply Tool diffs to ensure there are no instances of content corruption [ii] using the run the script @matmarex wrote and shared in T260393#6384098
This task should be worked on after 2-September, assuming T252558 is deployed on 2-September as we plan for it to be. [iii]
- Reply Tool diffs are inspected using the script @matmarex wrote and shared in T260393#6384098
- Any instances of Reply Tool edits causing changes other than content being added to the page are documented on this ticket
ii. These are two examples of the kind of content corruption we would expect to see more of if the "Issue 2" is NOT resolved: