Closed Bug 1572535 Opened 5 years ago Closed 5 years ago

New Tab and New Pocket Production Cluster Smoke Test

Categories

(Firefox :: New Tab Page, task, P1)

task

Tracking

()

RESOLVED FIXED

People

(Reporter: jirving, Unassigned, NeedInfo)

References

Details

The pocket backend could use some help from the firefox team. We are making some changes on our production cluster which host the APIs for FF New Tab. Before switching over we would like to run some sort of sanity check against this new cluster. Would it be possible to have someone on the firefox new tab team point a build/config to the new cluster and run a smoke check to confirm that there are no surprises in the behavior?

New cluster: https://production-web.readitlater.com

Jesh, what's the timeframe you need this by? Do you need it this week, or can we tackle sometime 8/19-8/30?

Flags: needinfo?(jesh)
Priority: -- → P1

To test that this works, we need to test three things, feeds, layouts, and spocs.

Helpful tools to test:

  1. In about:config Set browser.newtabpage.activity-stream.asrouter.devtoolsEnabled to true
  2. Go to about:home#devtools-ds
  3. This page lets you expire cache and look at the endpoint used for feeds, spocs, and layout, and when it was last fetched.

To test feeds:

  1. Set browser.newtabpage.activity-stream.discoverystream.endpoints to https://getpocket.cdn.mozilla.net/,https://spocs.getpocket.com/,https://production-web.readitlater.com/,https://gist.githubusercontent.com/
  2. Set browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://gist.githubusercontent.com/ScottDowne/896655ea2b387309ff1b821c6265ceb4/raw/a75aa336a610d548df6aa98d123df6b5eee14925/new-endpoint" }
  3. Ensure you see pocket stories and a message above them like "If you see spocs, and stories, we're goodHow it works"
  4. You can also verify it in about:home#devtools-ds under "Feeds Data" (nightly only)

To test layout

  1. Set browser.newtabpage.activity-stream.discoverystream.endpoints to https://getpocket.cdn.mozilla.net/,https://spocs.getpocket.com/,https://production-web.readitlater.com/
  2. Set browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://production-web.readitlater.com/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}
  3. Ensure you see three stories.
  4. No easy way to verify this in about:home#devtools-ds atm.

To test old spocs:

  1. Set browser.newtabpage.activity-stream.discoverystream.endpoints to https://getpocket.cdn.mozilla.net/,https://spocs.getpocket.com/,https://production-web.readitlater.com/
  2. Set browser.newtabpage.activity-stream.discoverystream.spocs-endpoint to https://production-web.readitlater.com/v3/firefox/unique-spocs
  3. Set browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":true,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}
  4. Ensure you see spocs.
  5. You can also verify it in about:home#devtools-ds under "spocs_endpoint" (nightly only)

Jesh - are we good here?

Yeah me and Daniel verified these.

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.