At account creation time, if the user is assigned variant C, the suggested edits module should be pre-initiated. In variant D, it's not pre-initiated.
|Open||MMiller_WMF||T238887 [EPIC] Growth: Homepage variant tests|
|Open||None||T246533 Variant tests: "initiation part 2" test (C vs. D)|
|Open||None||T250331 Variant tests: C-desktop|
|Open||None||T250440 Variant tests: C-mobile|
|Open||Catrope||T258023 Variant C: pre-initiate suggested edits module on account creation|
@Catrope -- I noticed something that needs to be fixed. When the user first arrives, there should be a pulsing blue dot on the topic filter button in the module (like we do in Variant A if someone initiates the module without having selected topics in the onboarding). Here's the original requirement from T250331: Variant tests: C-desktop:
- Suggested edits module
- The initiated suggested edits module is already present on the page upon arrival, including the pulsing blue dot on the topic filter.
- The module has an "i" icon in the upper right, which opens up the "Onboarding" sequence described below.
@MMiller_WMF before the patch, it looked like taskTypes=copyedit,links;topics=;taskCount=70;newcomerTaskToken=TOKEN
@Catrope made the patch to fix detection of when a user never set their topic filters (so that the user can see the pulsing blue dot), and that relies on using null instead of '' (empty string). We can adjust the newcomer task logging so that we output topics=; as it was before this patch, but it seems like null should be OK since we use that for taskCount currently (and I've also seen it for taskTypes although having trouble reproducing that; it seems like a bug).