Closed Bug 2065137 Opened 1 month ago Closed 26 days ago

Test the newtab searchbar SAP with a real search

Categories

(Firefox :: Search, task, P2)

task

Tracking

()

RESOLVED FIXED
157 Branch
Tracking Status
firefox157 --- fixed

People

(Reporter: dao, Assigned: dao)

References

Details

(Whiteboard: [sng][mcab-hnt])

Attachments

(2 files)

Follow-up from D319855.

browser_search_telemetry_sap_newtab_searchbar.js calls BrowserSearchTelemetry.recordSearch directly, so it exercises the recording path but not the New Tab search bar that is meant to reach it. It also asserts only browser.engagement.navigation.newtab_searchbar, while bug 2062210 added the SAP to browser.search.content, browser.search.withads and browser.search.adclicks too.

Drive a real search through the New Tab search bar and assert with SearchUITestUtils.assertSAPTelemetry, covering each metric the SAP was added to.

Depends on: 2062211
No longer depends on: 2062215
Blocks: 2062211
Depends on: 2062215
No longer depends on: 2062211
Severity: -- → N/A
Priority: -- → P2
Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED
Attachment #9632645 - Attachment description: Bug 2065137 - Let promiseSuggestionsPresent find suggestions in a content-process urlbar. r?mbeier! → Bug 2065137 - Let promiseSuggestionsPresent find suggestions in a content-process urlbar. r?#urlbar-reviewers!
Attachment #9632645 - Attachment description: Bug 2065137 - Let promiseSuggestionsPresent find suggestions in a content-process urlbar. r?#urlbar-reviewers! → Bug 2065137 - Let promiseSuggestionsPresent find suggestions in a content-process urlbar. r?mbeier!
Blocks: 2068055
Status: ASSIGNED → RESOLVED
Closed: 26 days ago
Resolution: --- → FIXED
Target Milestone: --- → 157 Branch
QA Whiteboard: [search][qa-triage-done-c157/b156]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: