Currently GrowthExperiments makes use of ExperimentUserManager or ExperimentUserDefaultsManager in a number of places (bespoke system) and also use of ExperimentTestKitchenManager in some others. We should move all experiment-able features to make use of the new system ExperimentTestKitchenManager. Or even more ambitiously, consider completely removing TestKitchen as a soft-dependency of GrowthExperiments and write all experiment code in WikimediaEvents.
To do so it would come very handy to have a product decision on each feature, should the feature remain AB-testable or should we get rid of the AB-testing setup for it?
Features affected
- SiteNoticeGenerator
- Task types (currently used for Revise Tone)
- Leveling up notifications
- Account creation section KPI dashboard
"Files" affected
- SiteNoticeGenerator, SiteNoticeGeneratorTest
- NewcomerTaskUserOptionsLookup, NewcomerTaskUserOptionsLookupTest (task type AB testing)
- SuggestedEdits.php (support for Revise tone experiment) — stays as it is until experiment concludes
- ExperimentsHooks (support for experiments using wgConditionalUserOptions)
- HomepageHooks (support for Account creation section in Growth KPI dashboard, support for $geForceVariant )
Acceptance criteria
- ExperimentUserManager is removed
- ExperimentUserDefaultsManager is removed
- Features that have been deemed not relevant to AB test anymore do not make use of any experiments manager