update browser_save_private_link_perwindowpb.js to use BrowserTestUtils

RESOLVED FIXED in Firefox 48

Status

()

RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: mixedpuppy, Assigned: mixedpuppy)

Tracking

46 Branch
Firefox 48
Points:
---

Firefox Tracking Flags

(firefox48 fixed)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

3 years ago
Created attachment 8739254 [details] [diff] [review]
modernize and clarify test

While trying to determine where a linux-debug-only-leak was happening (triggered by the test being updated) I rewrote this test to make it understandable.  Ultimately the the change is not necessary to fix the leak, but this is definitely more readable than before.
(Assignee)

Updated

3 years ago
Attachment #8739254 - Attachment is patch: true
Attachment #8739254 - Attachment mime type: text/x-patch → text/plain
(Assignee)

Updated

3 years ago
Attachment #8739254 - Flags: review?(jaws)
Assignee: nobody → mixedpuppy
Status: NEW → ASSIGNED
Summary: update test to use browsertestutils → update browser_save_private_link_perwindowpb.js to use BrowserTestUtils
Comment on attachment 8739254 [details] [diff] [review]
modernize and clarify test

Review of attachment 8739254 [details] [diff] [review]:
-----------------------------------------------------------------

::: browser/base/content/test/general/browser_save_private_link_perwindowpb.js
@@ +50,4 @@
>  
> +    function onTransferComplete(downloadSuccess) {
> +      ok(downloadSuccess, "Image file should have been downloaded successfully ");
> +  

nit, trailing whitespace

@@ +81,5 @@
>  }
>  
> +add_task(function* () {
> +  let testURI = "http://mochi.test:8888/browser/browser/base/content/test/general/bug792517.html";
> +  let newwindow = yield BrowserTestUtils.openNewBrowserWindow({private: true});

s/newwindow/privateWindow/
Attachment #8739254 - Flags: review?(jaws) → review+
(Assignee)

Comment 6

2 years ago
Created attachment 8743490 [details] [diff] [review]
modernize and clarify test

comments addressed and previous failure fixed by reverting the cache checking to what it was before.  carrying forward r+
Attachment #8739254 - Attachment is obsolete: true
Attachment #8743490 - Flags: review+

Comment 8

2 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/4e06b7965443
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
status-firefox48: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 48
You need to log in before you can comment on or make changes to this bug.