Standardize /urlbar/tests names
Categories
(Firefox :: Address Bar, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: bugzilla, Assigned: bugzilla)
References
Details
Attachments
(2 files, 2 obsolete files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
24.00 KB,
patch
|
Details | Diff | Splinter Review |
Our test names in urlbar/tests
aren't standardized. Many are browser_urlbar_testName.js
, but there are also a bunch of browser_urlbarTestName.js
, and browser_testName.js
. There's also a few browser_otherComponentName_testName.js
, like browser_switchTab_override.js
. Bug 1616631 added a urlbar/tests/browser/tips
folder and the test names in there are also not standardized.
It would be nice if all our tests followed the browser_componentName_testName.js
convention, where componentName
is urlbar
in most cases.
We should avoid oversimplification (e.g. browser_testName.js
) since that could lead to conflicts with tests in other folders now or in the future. This would likely lead to undefined behaviour with the mach
feature that allows you to run a test without specifying the pathname, for example mach mochitest browser_urlbar_interventions.js
.
Comment 1•6 years ago
|
||
I'd like to vote for not including "urlbar" in the names... :-) It's just noise since all these tests are in the urlbar directory. The point about the mach feature is good though, but I'd argue if two tests have the same name, mach should let you disambiguate somehow and if it doesn't then that's a deficiency in mach.
Comment 2•6 years ago
•
|
||
Deciding on a name format for the future would be nice.
I'm also in favor of non duplicating what is in the path, reason for which I preferred to not change test names in Bug 1616631 to contain tip because they are in a tips/ folder. We should probably remove the urlbar part from some tests.
If this brings to some renaming, we should just pay attention to update intermittent failure bugs to track both names.
It sounds like we should file a bug against mach to provide a choice when multiple tests with the same name exist (show options with full path and allow to pick one by number). In general it's really easy to just get the relative path of a test from text editors (also VS Code on Windows has an add-on to get unix style relative path), so I'm not particularly worried about that.
Assignee | ||
Comment 3•6 years ago
|
||
I'll move forward with dropping urlbar
from the names. For example urlbar/tests/browser/browser_urlbar_suggestedIndex.js
will become urlbar/tests/browser/browser_suggestedIndex.js
; and urlbar/tests/browser/browser_urlbarAboutHomeLoading.js
will become urlbar/tests/browser/browser_aboutHomeLoading.js
. Tests that refer to another component or feature, such as browser_switchTab_override.js
, will remain unchanged.
Assignee | ||
Comment 4•6 years ago
|
||
Marco suggested I rename these open bugs, or else do not rename those tests.
I decided to not rename browser_urlbar_event_telemetry
and browser_urlbar_selection
, just to avoid making unwieldy or too many changes to bugs. For the test of the bugs linked, I'll rename the bug or else they aren't tests in components/urlbar/tests
. I'll rename the bugs after this one passes review.
Assignee | ||
Comment 5•6 years ago
|
||
Assignee | ||
Comment 7•6 years ago
|
||
Depends on D65192
Comment 8•6 years ago
|
||
Backed out changeset cd6f62b46de2 (bug 1618867) for browser-chrome failures at browser/components/urlbar/tests/browser/browser_search_favicon.js
Backout: https://hg.mozilla.org/integration/autoland/rev/563b29d5921f63efa338188a067e08a0f96025a0
Failure push: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=cd6f62b46de2b8251689f2ab7799f84efef71231
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=291682552&repo=autoland&lineNumber=36573
Updated•6 years ago
|
Assignee | ||
Comment 9•6 years ago
|
||
I have a new revision up that rolls up the changes from the hotfix.
Try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=326e66d0338349e9059fea45fa9146a29b8c1971
Comment 10•6 years ago
|
||
Comment 11•6 years ago
|
||
Backed out for build bustages
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=292019413&repo=autoland&lineNumber=1239
Backout: https://hg.mozilla.org/integration/autoland/rev/565b8e750095a729377c287c75525c8304f0147b
Assignee | ||
Comment 12•6 years ago
|
||
Sorry about that. This got tangled up in dependencies with bug 1620274 and I didn't double-check what I was pushing when all the rebasing was through.
Here's a new try run with both patches: https://treeherder.mozilla.org/#/jobs?repo=try&revision=b26b98716d7347ef333ab0f0ec28ad60faa02b2b
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
Backed out changeset 5b82efb2a20f (bug 1618867) for causing multiple build bustages on tips/browser.ini
Bckout revision https://hg.mozilla.org/integration/autoland/rev/ed30fd3c5b148c3c7b3419da662b1063e098d3f7
Failure log https://treeherder.mozilla.org/logviewer.html#?job_id=292037201&repo=autoland
Harry can you please take a look?
Assignee | ||
Comment 15•6 years ago
|
||
Oh, this is weird: autoland shows just one .ini file changed, when this patch should touch 50+ files. Phabricator shows that I'm editing all 50+ files. I'll investigate...
Assignee | ||
Comment 16•6 years ago
|
||
Okay, something went wrong with the VC on that revision. Not entirely sure what. I downloaded the raw diff from the old Phabricator and I'm just going to start fresh with a new Phabricator revision.
Assignee | ||
Comment 17•6 years ago
|
||
Updated•6 years ago
|
Assignee | ||
Comment 18•5 years ago
|
||
Try run with just the patch in this bug: https://treeherder.mozilla.org/#/jobs?repo=try&revision=d00b0f1a87f1fc5b90d62640eadaed2c20e0e843
With bug 1620274 on top: https://treeherder.mozilla.org/#/jobs?repo=try&revision=8274a583de96272d54f5648e49254aaa593f0768
Comment 19•5 years ago
|
||
Comment 20•5 years ago
|
||
Backed out changeset ef16e75c0df3 (bug 1618867) for build bustages in urlbar/tests/browser/tips/browser.ini
Push that started the failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=superseded%2Ctestfailed%2Cbusted%2Cexception%2Crunnable&revision=ef16e75c0df3f65aad0a038d8582fefc70a01e40&selectedJob=292365019
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=292365019&repo=autoland&lineNumber=1428
Backout: https://hg.mozilla.org/integration/autoland/rev/9d8ced53ad75cc8afd207d9f7f65ed5129e9a6df
Assignee | ||
Comment 21•5 years ago
|
||
The same thing I noted in comment 15 happened again. I contacted the Conduit team and they're stumped. They recommended I just upload a diff and land with checkin-needed. Sorry about the noise on this bug!
Assignee | ||
Updated•5 years ago
|
Comment 22•5 years ago
|
||
Updated•5 years ago
|
Comment 23•5 years ago
|
||
Backed out changeset 66950fa024e1 (Bug 1618867) for causing build bustages in /builds/worker/checkouts/gecko/browser/components/urlbar/tests/browser/tips/browser.ini CLOSED TREE
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=292670187&repo=autoland&lineNumber=1431
Comment 24•5 years ago
|
||
Assignee | ||
Comment 25•5 years ago
|
||
The issue here is that I was renaming the file browser_URLBarSetURI.js
, but another patch renamed it to browser_UrlbarInput_setURI.js
beneath me. Lando didn't catch this; this is being worked on in bug 1621284.
I'm preparing a patch that won't touch this file.
Assignee | ||
Comment 26•5 years ago
|
||
There's a new revision on Phabricator that does not touch browser_URLBarSetURI.js
or browser_UrlbarInput_setURI.js
and applies cleanly to central. Try run: https://treeherder.mozilla.org/#/jobs?repo=try&revision=cc9fcf8facf7f20195c4c8c54444ba0fe23ff8f7.
Assignee | ||
Updated•5 years ago
|
Comment 27•5 years ago
|
||
Comment 28•5 years ago
|
||
bugherder |
Assignee | ||
Updated•5 years ago
|
Description
•