Closed Bug 1553236 Opened 1 year ago Closed 1 year ago

Change unit test callers for nsISearchService.addEngineWithDetails to use object passing rather than individual parameters


(Firefox :: Search, task, P3)




Firefox 69
Tracking Status
firefox69 --- fixed


(Reporter: standard8, Assigned: melvingeorge10, Mentored)



(Whiteboard: [good first bug][lang=js])


(1 file, 1 obsolete file)

nsISearchService.addEngineWithDetails currently supports two formats of parameters:, iconURL, alias, description, method, template, extensionID);

or, details);

We want to migrate to using just the name, details form. To start off with, lets do just the unit tests, here's a link to the current places this affects:

I'm opening this up as mentored. To help Mozilla out with this bug, here's the steps:

  1. Comment here on the bug that you want to volunteer to help. I (or someone else) will assign it to you.
  2. Download and build the Firefox source code: (an artifact build is sufficient).
  3. Start working on this bug.
    • See the link in comment 0 for the places to change. We want to change calls such as
await"MozSearch", "", "mozalias", "", "GET",


await"MozSearch", {
  alias: "mozalias",
  method: "GET",
  template: "{searchTerms}",
* Note: you'll need to use different properties in the object depending on what the original call was. See the [documentation here]( for the possible parameter names.
* If a parameter is "" or null, then it doesn't need specifying in the object.
* If you have direct questions about this bug, feel free to ask here or on irc.
  1. Check your changes for adherence to our guidelines by using:
    • ./mach lint --workdir
      • (this checks the uncommited changes in your work directory)
  2. Build your change with mach build and test your change with:
    • ./mach test toolkit/components/search
    • You can also name the other directories where there are files that you're changing, but we'll also run these against our test servers once a patch has been posted to make sure nothing has broken.
  3. Submit the patch for review. Mark me as a reviewer (r?standard8) so I'll get an email to come look at your code.
  4. After a series of reviews and changes to your patch, I'll mark it for checkin or push it to autoland. Your code will soon be shipping to Firefox users worldwide!
  5. you get to think about what kind of bug you'd like to work on next. Let me know what you're interested in and I can help you find your next contribution.
Mentor: standard8
Whiteboard: [good first bug][lang=js]

I would like to work on this issue.

Welcome, please start working on it, and let us know if you get any issues.

Assignee: nobody → melvingeorge10

can you please point out the repository i need to start working on.

(In reply to melvingeorge10 from comment #4)

can you please point out the repository i need to start working on.

If you follow the link in step 1 (i.e., pick the platform that you're starting on.

Then near the top of the page, it'll tell you what you need to do to get set up, and what commands you need to run to clone the repository (Generally in a "Get the source"/"Get the code" section).

i need only mozilla-central repo.. but the script downloads mozilla-unified repo

Unified is a superset of mozilla-central, so it doesn't matter except it is larger. If you want just mozilla-central, then use:

hg clone


Depends on D32565

Made all the changes to initial revision. ( D32565 - )

Attachment #9067843 - Attachment is obsolete: true
Attachment #9067532 - Attachment description: Bug 1553236 - made all test suites containing search.addEngineWithDetails() function to use with object parameters r=standard8 → Bug 1553236 - Change tests using to use the object parameter form. r=standard8
Pushed by
Change tests using to use the object parameter form. r=Standard8
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 69
You need to log in before you can comment on or make changes to this bug.