This task is for tracking how we test/QA the new EditorJourney schema, as well as our ability to use its data along with the data from other relevant schemas. If we find bugs, we should file those separately. On this task, we'll just discuss issues related to our ability to test.
These are our plans:
* @Etonkovidova will test in Korean and English Beta Labs.
** {icon exclamation-triangle color=red} Testing in mobile to make sure that things are recorded correctly and the is_mobile flag is set to true.
** Looking for whether events are recorded from the EditorJourney schema according to the business rules laid out on the [[ https://meta.wikimedia.org/wiki/Schema_talk:EditorJourney | schema talk page ]].
** In particular, it will be important to ensure that the right URLs are and are not being obfuscated according to these namespaces:
*** Obfuscated
**** {icon check-square color=green} Article (0)
**** {icon check-square color=green} Article talk (1)
**** {icon check-square color=green} File (6)
**** {icon check-square color=green} File talk (7)
**** {icon exclamation-triangle color=red} Portal (100)
**** {icon exclamation-triangle color=red} Portal (101)
**** {icon exclamation-triangle color=red} Draft (118)
**** {icon exclamation-triangle color=red} Draft talk (119)
*** {icon check-square color=green} Not obfuscated (all others, including the following)
**** Help (12)
**** Help talk (13)
**** Wikipedia (4)
**** Wikipedia talk (5)
**** User (2)
**** User talk (3)
**** Special (-1)
**** [all others] e.g. Template (10)
** {icon check-square color=green} Verifying that this is only recording events for accounts less than 24 hours old. Events should stop after 24 hours.
** {icon check-square color=green} Verify that we log events when someone goes to change their email in Preferences.
** {icon check-square color=green} Verify that we log events for when someone does an action from the View History page of an article.
** It would probably be good to test out this sequence of activities, to make sure that it can be reconstructed from the events. Here is an example sequence.
*** {icon check-square color=green} 1) User creates account from editing context.
*** {icon check-square color=green} 2) After account creation, user lands back on article in editing context. URL should be obfuscated with a hash, but the action should specify "edit".
*** {icon check-square color=green} 3) User clicks a link in the article and see another article. URL should be obfuscated with a different hash.
*** {icon check-square color=green} 4) User clicks back button to go back to first article. URL should be obfuscated with the same hash as before.
*** 5) User clicks "Help" in the left nav. URL should not be obfuscated.
*** {icon check-square color=green} 6) User searches the title of the article they were originally on. URL should be obfuscated with the same hash as before.
*** {icon check-square color=green} 7) User clicks "View history". Event should include a "history" action.
*** {icon check-square color=green} 8) User clicks on a username in the history list and goes to a User page. URL should not be obfuscated.
*** {icon check-square color=green} 9) User clicks back and returns to article, and then clicks "Talk". URL should be obfuscated with a different hash than the "Article" page.
* @nettrom_WMF will also test in Korean and English Beta Labs.
** Focusing on whether the events recorded are usable for answering the questions listed on T205758.
** Also verifying that the new schema is usable with the other schemas we need to use in conjunction with it to give us the full picture of the user's journey.
** Can use the queries from T206182 to do test driven development.
* Other engineers from the team can also help test.