test(ntp): add regression coverage for Customize Responses tools menu

[cursor]

Asana Task/Github Issue: Regression test coverage automation (cron)

Description

Adds integration tests for the recently merged Customize Responses Tools-menu feature (#2865). That PR introduced config-driven visibility, native messaging hooks, an apply toggle, and interaction constraints — but shipped without dedicated test coverage.

Risky behavior now covered

• Feature-flag gating (enableCustomizeResponses)
• Custom sublabel vs default description rendering
• omnibar_openCustomizeResponses notification when the row is selected
• Apply toggle visibility when hasCustomization is set
• omnibar_setCustomizeResponsesActive notifications on toggle on/off
• Collapsed (icon-only) Tools button when customization is active
• Row disabled while image-generation mode is active

Test files added/updated

• special-pages/pages/new-tab/app/omnibar/integration-tests/omnibar.spec.js — 9 new tests in AI chat customize responses describe block
• special-pages/pages/new-tab/app/omnibar/integration-tests/omnibar.page.js — page object helpers for menu item and toggle

Why these tests materially reduce regression risk

The Customize Responses flow spans config parsing, Tools-menu composition (useToolsMenu / useCustomizeResponsesItem), native messaging, and cross-tool state (image-generation disables the row). A regression in any of these would silently break AI personalization UX or send incorrect native notifications. These tests exercise the full user-visible path and assert the native bridge payloads.

Testing Steps

cd special-pages
npm run build -- --page=new-tab
npm run test-int -- pages/new-tab/app/omnibar/integration-tests/omnibar.spec.js --grep "AI chat customize responses" --reporter list

All 9 tests pass.

Checklist

• 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

  

[github-actions]

Build Branch

Branch	pr-releases/cursor/regression-test-coverage-automation-8e6f
Commit	4ccfae94cb
Updated	July 20, 2026 at 8:04:05 AM UTC

Static preview entry points

• Docs: docs/index.html
• Static pages: build/integration/pages/index.html
• Integration pages: injected/integration-test/test-pages/index.html

QR codes (mobile preview)

Entry point	QR code
Docs
Static pages
Integration pages

Integration commands

npm (Android / Extension):

npm i github:duckduckgo/content-scope-scripts#pr-releases/cursor/regression-test-coverage-automation-8e6f

Swift Package Manager (Apple):

.package(url: "https://github.com/duckduckgo/content-scope-scripts.git", branch: "pr-releases/cursor/regression-test-coverage-automation-8e6f")

git submodule (Windows):

git -C submodules/content-scope-scripts fetch origin pr-releases/cursor/regression-test-coverage-automation-8e6f
git -C submodules/content-scope-scripts checkout origin/pr-releases/cursor/regression-test-coverage-automation-8e6f

Pin to exact commit

npm (Android / Extension):

npm i github:duckduckgo/content-scope-scripts#4ccfae94cb7e493fc6e4c11e33dc427c58b3e413

Swift Package Manager (Apple):

.package(url: "https://github.com/duckduckgo/content-scope-scripts.git", revision: "4ccfae94cb7e493fc6e4c11e33dc427c58b3e413")

git submodule (Windows):

git -C submodules/content-scope-scripts fetch origin pr-releases/cursor/regression-test-coverage-automation-8e6f
git -C submodules/content-scope-scripts checkout 4ccfae94cb7e493fc6e4c11e33dc427c58b3e413

[github-actions]

[Beta] Generated file diff

Time updated: Mon, 20 Jul 2026 08:04:58 GMT