Change Details

== Background During the reading list experiment, we created desktop and mobile instrumentation to track usage of the feature. We need to transition them to permanent instrumentation in order to track usage trends as a beta feature. The experimentation platform team has created some [[ https://wikitech.wikimedia.org/wiki/Test_Kitchen/Conduct_an_experiment#Convert_experiment_to_baseline_instrument | documentation ]] around how to do so, although some of the strings still say "xLab" when it's possible that this needs to be updated to the newest name: test kitchen. === Design requirements //Add design requirements or link to design files.// --- == Requirements === Acceptance criteria - [] //Add clear acceptance criteria.// === BDD - //For QA engineer to fill out.// === Test Steps - //For QA engineer to fill out.// === Communication criteria //Add if this needs an announcement or discussion.// === Rollback plan //Describe the rollback plan in production for this task if something goes wrong.// //This task was created by Version 1.0.0 of the Reader Experience team task template using [[ https://phabulous.toolforge.org/ | phabulous ]].//

== Background During the reading list experiment, we created desktop and mobile instrumentation to track usage of the feature. We need to transition them to permanent instrumentation in order to track usage trends as a beta feature. The experimentation platform team has created some [[ https://wikitech.wikimedia.org/wiki/Test_Kitchen/Conduct_an_experiment#Convert_experiment_to_baseline_instrument | documentation ]] around how to do so, although some of the strings still say "xLab" when it's possible that this needs to be updated to the newest name: test kitchen. NOTE: this will encompass switching the custom stream we created to the web stream as we can now select custom contextual attributes via the UI with the instrument workflow === Design requirements //Add design requirements or link to design files.// --- == Requirements === Acceptance criteria - [] //Add clear acceptance criteria.// === BDD - //For QA engineer to fill out.// === Test Steps - //For QA engineer to fill out.// === Communication criteria //Add if this needs an announcement or discussion.// === Rollback plan //Describe the rollback plan in production for this task if something goes wrong.// //This task was created by Version 1.0.0 of the Reader Experience team task template using [[ https://phabulous.toolforge.org/ | phabulous ]].//

== Background During the reading list experiment, we created desktop and mobile instrumentation to track usage of the feature. We need to transition them to permanent instrumentation in order to track usage trends as a beta feature. The experimentation platform team has created some [[ https://wikitech.wikimedia.org/wiki/Test_Kitchen/Conduct_an_experiment#Convert_experiment_to_baseline_instrument | documentation ]] around how to do so, although some of the strings still say "xLab" when it's possible that this needs to be updated to the newest name: test kitchen. NOTE: this will encompass switching the custom stream we created to the web stream as we can now select custom contextual attributes via the UI with the instrument workflow === Design requirements //Add design requirements or link to design files.// --- == Requirements === Acceptance criteria - [] //Add clear acceptance criteria.// === BDD - //For QA engineer to fill out.// === Test Steps - //For QA engineer to fill out.// === Communication criteria //Add if this needs an announcement or discussion.// === Rollback plan //Describe the rollback plan in production for this task if something goes wrong.// //This task was created by Version 1.0.0 of the Reader Experience team task template using [[ https://phabulous.toolforge.org/ | phabulous ]].//