NTP: Expand screenshot tests

[noisysocks]

Asana Task/Github Issue:

Description

Expands the NTP screenshot tests to cover more states. That way we can be more confident that #2095 isn’t breaking anything.

Testing Steps

n/a

Checklist

Please tick all that apply:

• I have tested this change locally
• I have tested this change locally in all supported browsers
• This change will be visible to users
• I have added automated tests that cover this change
• I have ensured the change is gated by config
• This change was covered by a ship review
• This change was covered by a tech design
• Any dependent config has been merged

---

Note

Greatly expands NTP screenshot coverage, makes omnibar visible by default (hide with omnibar=false), adds array query param support, and updates tests/config accordingly.

• Screenshots/Tests:
  • Expand NTP screenshots to cover: omnibar (search/AI states, suggestions, focus, overflow, customize popover), customizer drawer (AI enabled/disabled/hidden setting), favorites (many collapsed/expanded, single, empty), privacy stats (few, cpm), activity (default/empty), update notification (empty/populated), RMF (small/medium/big variants), next steps (two cards), freemium PIR banner (onboarding/scan results), subscription winback (last day).
  • Update/rename screenshots accordingly and remove old omnibar "omnibar=true"-dependent suite.
• Playwright config:
  • Move NTP screenshots into dedicated projects: ntp-screenshots-light and ntp-screenshots-dark with set viewport and color scheme.
• Mock/Initialization:
  • Change initialSetup to include omnibar by default; only omit when omnibar='false'.
• Test helpers:
  • NewtabPage.openPage supports array values in additional (appends multiple params).
• Integration tests:
  • Update expectations to include omnibar in widgets_setConfig and context menu.
  • Adjust favorites tests to pass omnibar: 'false' where needed for deterministic focus order.

^{Written by Cursor Bugbot for commit 5943ec7. This will update automatically on new commits. Configure here.}

[netlify]

✅ Deploy Preview for content-scope-scripts ready!

Name	Link
🔨 Latest commit	5943ec7
🔍 Latest deploy log	https://app.netlify.com/projects/content-scope-scripts/deploys/693a6c52f08b7c27b0adf0c0
😎 Deploy Preview	https://deploy-preview-2096--content-scope-scripts.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

Temporary Branch Update

The temporary branch has been updated with the latest changes. Below are the details:

• Branch Name: pr-releases/pr-2096
• Commit Hash: d45892b5c3e905604d48c8b56e5a4a9c6346920f
• Last Updated: December 10, 2025 at 10:42:11 PM UTC
• Install Command: npm i github:duckduckgo/content-scope-scripts#d45892b5c3e905604d48c8b56e5a4a9c6346920f

Please use the above install command to update to the latest version.

[github-actions]

[Beta] Generated file diff

Time updated: Wed, 10 Dec 2025 22:42:35 GMT

Integration

    - integration/pages/new-tab/dist/index.js

File has changed

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[shakyShane]

@noisysocks thanks for this!

I agree we should increase the coverage - but my request is that we optimise the approach for future debugging/changes instead. I think in this case we should use playwrights projects/fixtures support to avoid the forEach calls in the code.

Tests are the place I don’t want to be DRY, I want debugging super powers instead.

That might mean setting up a project for light screenshots, and then dark etc. I’m not sure exactly on how to solve this, but anything that removes the loops will work.