Bug 1546492 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

QA steps to test lifetime and period frequency cap:

1. about:config and reset browser.newtabpage.activity-stream.discoverystream.spoc.impressions so it's {}, (from a clean profile,  in  browser.newtabpage.activity-stream.discoverystream.config layout_variant as basic and set hardcoded_layout as false)
2. open a new tab and note spoc story shown
3. check that the pref from step 1 is no longer just {} and is probably something like {"790":[1556134274653]} where 790 is campaign_id of the spoc story shown

4. Open JSON by using layout variant link from config
e.g. https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=basic

Click on feed url link inside CardGrid component e.g. https://getpocket.cdn.mozilla.net/v3/firefox/global-recs?version=3&consumer_key=40249-e88c401e1b1f2242d9e441c4&locale_lang=en-US&feed_variant=default_spocs_on

5. Open spoc item from spocs array with campaign id from step 3 and note values inside caps object 

6. To test capping count within a period, refresh new tab to count given in caps->campaign -> count, time stamp should get appended to pref in step 1 for same campaign_id till the value seen in campaign count

7. To test the life time cap change clock to time more than campaign->period (in seconds)

8. restart firefox
9. initial home page probably is still showing the same stories (as it'll show cached stories while fetching the new ones)

10. refresh the page and spoc story in step 3 should show till lifetime count is met. Pref should be updated to reflect timestamp entries equivalent to lifetime count for that campaign_id
QA steps to test lifetime and period frequency cap:

1. about:config and reset browser.newtabpage.activity-stream.discoverystream.spoc.impressions so it's {}, (from a clean profile,  in  browser.newtabpage.activity-stream.discoverystream.config layout_variant as basic and set hardcoded_layout as false)
2. open a new tab and note spoc story shown
3. check that the pref from step 1 is no longer just {} and is probably something like {"790":[1556134274653]} where 790 is campaign_id of the spoc story shown

4. Open JSON by using layout variant link from config
e.g. https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=basic

Click on feed url link inside CardGrid component e.g. https://getpocket.cdn.mozilla.net/v3/firefox/global-recs?version=3&consumer_key=40249-e88c401e1b1f2242d9e441c4&locale_lang=en-US&feed_variant=default_spocs_on

5. Open spoc item from spocs array with campaign id from step 3 and note values inside caps object 

6. To test capping count within a period, refresh new tab to count given in caps->campaign -> count, time stamp should get appended to pref in step 1 for same campaign_id till the value seen in campaign count. After campaign count is met, spoc story should be replaced by a new spoc story.

7. To test the life time cap change clock to time more than campaign->period (in seconds)

8. restart firefox
9. initial home page probably is still showing the same stories (as it'll show cached stories while fetching the new ones)

10. refresh the page and spoc story in step 3 should show till lifetime count is met. Pref should be updated to reflect timestamp entries equivalent to lifetime count for that campaign_id. After lifetime count is met, spoc story should be replaced by a new spoc story.

Back to Bug 1546492 Comment 3