Closed Bug 1910209 Opened 3 months ago Closed 3 months ago

Improve the Fakespot suggestions engagement telemetry test

Categories

(Firefox :: Address Bar, task, P2)

task

Tracking

()

RESOLVED FIXED
131 Branch
Tracking Status
firefox131 --- fixed

People

(Reporter: adw, Assigned: adw)

References

Details

Attachments

(1 file)

I have a small patch to improve the Fakespot suggestions engagement telemetry test.

Summary: Improve the Fakespot suggestions browser test → Improve the Fakespot suggestions engagement telemetry test

The main thing this does is add a task to the Fakespot engagement telemetry test
that triggers both a Fakespot and history result and then clicks the history
result. I want to make sure the Fakespot engagement event isn't incorrectly
recorded. (I thought it might be but it's not.)

This also has a bunch of changes from http to https. Lint made me change the
URLs in the Fakespot test to https, which was a problem for the AMP result since
QuickSuggestTestUtils.ampRemoteSettings() uses http URLs. So I went ahead and
updated that function plus the other ones and all the places that are affected.

The UrlbarUtils change makes UrlbarTestUtils.getDetailsOfResultAt
return the right URL for Fakespot results. No tests fail with this change and it
seems like the right thing to do anyway.

Depends on D217780

See Also: → 1911683
Pushed by dwillcoxon@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/edd40fa188c5 Improve the Fakespot suggestions engagement telemetry test and use https URLs in more Suggest tests. r=daisuke
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → 131 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: