Change Details

== Background Now that the AB test is over, we want to make sure we remove the code we wrote. This includes: [x] Hooks firing in MobileFrontend and RelatedArticles [x] Bucketing code in RelatedArticles [x] Eventstream configuration [x] AB test schema https://gerrit.wikimedia.org/r/c/1138859 [] Instrumentation in WikimediaEvents https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikimediaEvents/+/1141954 [] AB flag configuration https://gerrit.wikimedia.org/r/c/mediawiki/extensions/RelatedArticles/+/1141989 [] all other styles/js/html we wrote for this code https://gerrit.wikimedia.org/r/c/mediawiki/extensions/RelatedArticles/+/1141989 == User story - As a developer, we want to avoid accumulating tech debt and unused code so we can deliver features faster == Requirements - No visual changes - All code and references to the search Ab test code are removed == Design == Acceptance criteria - No search ab test events are firing - no search ab enrollment is happening

== Background Now that the AB test is over, we want to make sure we remove the code we wrote. This includes: [x] Hooks firing in MobileFrontend and RelatedArticles [x] Bucketing code in RelatedArticles [] Instrumentation in WikimediaEvents [x] Eventstream configuration [] AB flag configuration [] AB test schema [] all other styles/js/html we wrote for this code == User story - As a developer, we want to avoid accumulating tech debt and unused code so we can deliver features faster == Requirements - No visual changes - All code and references to the search Ab test code are removed == BDD ``` Feature: Mobile search continues to function after removing AB test code Scenario: Search field interaction functions as before Given I am an anonymous user on mobile When I tap the search field Then the standard type-ahead search suggestions should appear And no empty-state recommendations are shown Scenario: Search results display correctly after typing Given I enter a search query in the search field When the results populate Then I see relevant results with no visual regressions or JS errors ``` == Test Steps Test Case 1: Verify search behaves normally without A/B test features 1. Visit https://en.m.wikipedia.beta.wmflabs.org on a mobile viewport. 2. Tap the search bar on the main page. 3. Type in a search term like “Dog”. 4. Confirm that standard type-ahead suggestions appear. 5. AC1: Confirm no empty search recommendations are shown. 6. AC2: Confirm type-ahead results show as expected. 7. AC3: Confirm no UI regressions or console errors occur. == Design == Acceptance criteria - No search ab test events are firing - no search ab enrollment is happening

== Background Now that the AB test is over, we want to make sure we remove the code we wrote. This includes: [x] Hooks firing in MobileFrontend and RelatedArticles [x] Bucketing code in RelatedArticles [] Instrumentation in WikimediaEvents [x] Eventstream configuration [x] AB test schema https://gerrit.wikimedia.org/r/c/1138859flag configuration [] Instrumentation in WikimediaEvents https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikimediaEvents/+/1141954AB test schema [] AB flag configuration https://gerrit.wikimedia.org/r/c/mediawiki/extensions/RelatedArticles/+/1141989 [] all other styles/js/html we wrote for this code https://gerrit.wikimedia.org/r/c/mediawiki/extensions/RelatedArticles/+/1141989 == User story - As a developer, we want to avoid accumulating tech debt and unused code so we can deliver features faster == Requirements - No visual changes - All code and references to the search Ab test code are removed == BDD ``` Feature: Mobile search continues to function after removing AB test code Scenario: Search field interaction functions as before Given I am an anonymous user on mobile When I tap the search field Then the standard type-ahead search suggestions should appear And no empty-state recommendations are shown Scenario: Search results display correctly after typing Given I enter a search query in the search field When the results populate Then I see relevant results with no visual regressions or JS errors ``` == Test Steps Test Case 1: Verify search behaves normally without A/B test features 1. Visit https://en.m.wikipedia.beta.wmflabs.org on a mobile viewport. 2. Tap the search bar on the main page. 3. Type in a search term like “Dog”. 4. Confirm that standard type-ahead suggestions appear. 5. AC1: Confirm no empty search recommendations are shown. 6. AC2: Confirm type-ahead results show as expected. 7. AC3: Confirm no UI regressions or console errors occur. == Design == Acceptance criteria - No search ab test events are firing - no search ab enrollment is happening