Replace BrowserTestUtils.waitForCondition with TestUtils.waitForCondition in browser_documentnavigation.js
Categories
(Firefox :: General, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox75 | --- | fixed |
People
(Reporter: prathiksha, Assigned: skanthavar, Mentored)
Details
Attachments
(1 file, 1 obsolete file)
This is a good first bug for newcomers to Firefox development.
BrowserTestUtils.waitForCondition in browser/base/content/test/general/browser_documentnavigation.js[0] can be replaced by TestUtils.waitForCondition.
You can run this test with the ./mach test command:
./mach test browser/base/content/test/general/browser_documentnavigation.js
Please leave a comment if you would like to be assigned to this bug. Feel free to contact us via Matrix in the #osfcep channel or leave a comment here if you're stuck.
Reporter | ||
Updated•4 years ago
|
Please let me know if I've understood this correct - This is a straight replacement of BrowserTestUtils
module with TestUtils
module because the waitForCondition
method of BrowserTestUtils
was just a reference to the same method defined in TestUtils
.
Also, are these the right steps to take?
- Make necessary changes
- Make sure the tests run fine and eslint doesn't complain
- Commit changes with an appropriate message
- Then push code to Phabricator
Is there any additional steps I should take like making another clone or have a different branch or pull requests of some sorts?
Sorry for all these questions. This is my first encounter with Mercurial and I am yet to read the docs to know how different it is from Git.
Reporter | ||
Comment 3•4 years ago
|
||
(In reply to skanthavar from comment #2)
Please let me know if I've understood this correct - This is a straight replacement of
BrowserTestUtils
module withTestUtils
module because thewaitForCondition
method ofBrowserTestUtils
was just a reference to the same method defined inTestUtils
.Also, are these the right steps to take?
- Make necessary changes
- Make sure the tests run fine and eslint doesn't complain
- Commit changes with an appropriate message
- Then push code to Phabricator
Is there any additional steps I should take like making another clone or have a different branch or pull requests of some sorts?
Sorry for all these questions. This is my first encounter with Mercurial and I am yet to read the docs to know how different it is from Git.
Yes, you have understood it correctly. Please just follow all the steps you just listed. There are no additional steps required. I am assuming that you have cloned the 'mozilla-central' repo using 'hg clone' and followed all setup instructions from our document.
Updated•4 years ago
|
Pushed by prathikshaprasadsuman@gmail.com: https://hg.mozilla.org/integration/autoland/rev/3893a9b0514c Replace BrowserTestUtils.waitForCondition with TestUtils.waitForCondition in browser_documentnavigation.js. r=prathiksha
Comment 7•4 years ago
|
||
bugherder |
Description
•