Closed Bug 1535999 Opened 6 years ago Closed 5 years ago

[Shield] Pref-Flip Study: activity-stream-pktnewtabH12019-release66smoketest1, 66, Release

Categories

(Shield :: Shield Study, enhancement)

enhancement
Not set
normal

Tracking

(firefox66- affected)

RESOLVED FIXED
Tracking Status
firefox66 - affected

People

(Reporter: experimenter, Assigned: nchapman)

References

Details

activity-stream-pktnewtabH12019-release66smoketest1

Limited study to be run on the first week of Release66 the check if there are any major bugs / unexpected behaviors with the:

  • discovery-stream API
  • Normandy targeting
  • telemetry

before upcoming Release66 Layouts study [1].

The study will consist of 4 branches (control + 3 different discoverystream layouts):

  • control
  • basic
  • complex
  • above-7-below-1

[1]: This study will be large and use a large portion of our eligible population so we want to mitigate bug risks by running this study.

More information: https://experimenter.services.mozilla.com/experiments/activity-stream-pktnewtabh12019-release66smoketest1/

[Tracking Requested - why for this release]:

Summary: [Shield] Pref-Flip Study: activity-stream-pktnewtabH12019-release66smoketest1 → [Shield] Pref-Flip Study: activity-stream-pktnewtabH12019-release66smoketest1, 66, Release

Pref-Flip Study: activity-stream-pktnewtabH12019-release66smoketest1 FF66 Release

Targeted: Firefox Release 66

Targeted: Firefox Release 67

We have finished testing the Pref-Flip Study: activity-stream-pktnewtabH12019-release66smoketest1 FF66 Release experiment.

Initially the testing was performed on Fx66 but we have noticed that the study duration will have 1 week overlap with Fx67. Because of this we extend our testing on Firefox Beta 67.0b3 also.

During testing we have found the following new issue:

Bug 1536812 - The user-friendly message is not displayed and the whole section is entirely collapsed if all the "Recommended by Pocket" cards are dismissed

QA’s recommendation: YELLOW - SHIP IT, CONDITIONALLY

Reasoning:

  • The experiment looks good overall and our extended testing on Fx67 uncovered only 1 new issue that is not considered major.

  • However, considering the fact that we didn't receive any answers to our two emails regarding Fx67 overlap, we are not sure if it is intended that the “Top Sites” menu functionality should be available for the experiment’s enrolled users starting with Firefox 67. This raised several concerns that generated the YELLOW sign-off.

Testing Summary:

Tested Platforms:

  • Windows 10 x64;

  • Mac OS 10.14.3;

  • Ubuntu 18.04 x64.

Tested Firefox versions:

  • Firefox Release 66.0

  • Firefox Beta 67.0b3

Flags: shield-qa+
Experiment Type: Pref Flip Study What is the preference we will be changing browser.newtabpage.activity-stream.discoverystream.config What are the branches of the study and what values should each branch be set to? - Treatment control 25%: Value: "{\"api_key_pref\":\"extensions.pocket.oAuthConsumerKey\",\"enabled\":false,\"show_spocs\":true,\"layout_endpoint\":\"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic\"}" Control, user gets current newtab/homepage experience (activitystream). Discoverystream is not used. - Treatment above-7-below-1 25%: Value: "{\"api_key_pref\":\"extensions.pocket.oAuthConsumerKey\",\"enabled\":true,\"show_spocs\":true,\"layout_endpoint\":\"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=66-release-2-above-7-below-1\"}" This is a more complex layout with a hero element on top and multiple topic columns below. - Treatment complex 25%: Value: "{\"api_key_pref\":\"extensions.pocket.oAuthConsumerKey\",\"enabled\":true,\"show_spocs\":true,\"layout_endpoint\":\"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=66-beta-2-complex\"}" Complex: pocket section has been expanded with multiple rows of content. - Treatment basic 25%: Value: "{\"api_key_pref\":\"extensions.pocket.oAuthConsumerKey\",\"enabled\":true,\"show_spocs\":true,\"layout_endpoint\":\"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic\"}" "Basic" variant of discoverystream, replicates the current experience, but does not include highlights section. What version and channel do you intend to ship to? 0.5% of Release Firefox 66.0 Are there specific criteria for participants? Locales: en-US Geographic regions: US Prefs: * please exclude any users with non-default values in the following prefs: - `browser.newtabpage.enable` - `browser.startup.homepage` - `browser.newtabpage.activity-stream.showSearch` - `browser.newtabpage.activity-stream.feeds.topsites` - `browser.newtabpage.activity-stream.feeds.section.topstories` - `browser.newtabpage.activity-stream.feeds.section.highlights` Studies: * N/A Any additional filters: * please exclude any users that have the Mozilla Dark Theme activated: `['environment']['addons']['activeAddons']['theme']['id']` is `'firefox-compact-dark@mozilla.org'` Please only include profiles in release that are 66 and 67. If they are FF68 and above, exclude them from the experiment. Note on population size: again, the purpose of this experiment is to check that everything related to the pref is working correctly on release. Hence, we don't care too much about the power of the experiment. As such, I'm targeting about 12,000 users in each branch, which should be 0.5% of the eligible population (roughly estimated here: https://dbc-caf9527b-e073.cloud.databricks.com/#notebook/64292/command/65044) What is your intended go live date and how long will the study run? Mar 25, 2019 - May 06, 2019 (42 days) What is the main effect you are looking for and what data will you use to make these decisions? What is the main effect you are looking for and what data will you use to make these decisions? What metrics are you using to measure success We are not looking for a specific effect, but we are looking to make sure that the metrics we will use are reporting as expected and in a reasonable range. Docs with metrics we will test here: * Topline Success Metrics: https://docs.google.com/document/d/1iMRp13mAXVPp4Am58HIRpWybIbVGT_1w9IbvDywZIUA/edit# * Dashboard and metrics of interest breakdown: https://docs.google.com/document/d/16wAKJ2d_ALLhwM5Os1DwVrkdwilCyw_AwrKWCaNmTLc/edit Do you plan on surveying users at the end of the study? Yes/No. Strategy and Insights can help create surveys if needed No Who is the owner of the data analysis for this study? shong@mozilla.com Will this experiment require uplift? False QA Status of your code: QA guidelines here: https://docs.google.com/document/d/1iySmNA2tBl3ApLuJtP7UBlPwNx9sH1SmK-jG6exvMQ0/edit#heading=h.s177b01wzbij Link to more information about this study: https://experimenter.services.mozilla.com/experiments/activity-stream-pktnewtabh12019-release66smoketest1/

Untracking since we have this information easily findable now in Experimenter.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.