[2026-09-03] eagle: work/projects/CPM Breakage Testing Steps.md
This commit is contained in:
@@ -19,8 +19,17 @@ Run each case with fresh app data so daily pixel deduplication does not hide res
|
||||
6. Navigate again → no additional CPM failure or recovery pixel is sent.
|
||||
|
||||
#### Session restoration
|
||||
1. Open a web page
|
||||
2. Dupli
|
||||
1. Open a web page, e.g. https://privacy-test-pages.site/features/autoconsent/banner.html
|
||||
2. Duplicate the tab twice (3 tabs are open)
|
||||
3. Open Settings → General, activate Reopen all windows and tabs from last session
|
||||
4. Restart the browser
|
||||
5. Open **Debug → Web Extensions → Simulate CPM Messaging Breakage (On)**
|
||||
6. Switch to another tab
|
||||
7. wait 5 seconds → `debug_web_extension_cpm_initialization_failed_after_session_restoration` is sent
|
||||
8. Switch to the remaining restored tab
|
||||
9. wait 5 seconds → `debug_web_extension_cpm_initialization_failed_after_session_restoration` is **skipped** (as it‘s daily): no `debug_web_extension_cpm_messaging_stuck…` is sent
|
||||
10. Reload the tab or navigate somewhere else
|
||||
11. wait 5 seconds → `debug_web_extension_cpm_initialization_failed_after_other` is sent; `debug_web_extension_cpm_messaging_stuck_session_restoration` is sent
|
||||
|
||||
#### Concurrent navigations
|
||||
|
||||
|
||||
Reference in New Issue
Block a user