Alphabetically order all FxMS test manifests
Categories
(Firefox :: Messaging System, task, P2)
Tracking
()
People
(Reporter: aminomancer, Assigned: rchan, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug)
Attachments
(1 file)
We're frequently getting Mozlint test-manifest warnings on phabricator because a new rule was added:
WARNING: The mochitest test manifest is not in alphabetical order. Expected ordering:
And basically it wants fully alphabetized ordering. But this isn't something that should be fixed within a patch that was focused on something else and just adds a test. Now, I think when mochitest runs a full manifest, it actually runs them in alphabetical order even if the list is not alphabetized (correct me if I'm wrong). So I don't think fixing the order would actually cause any problems. But if it does, it just seems safest to handle that in a dedicated patch so we can track and troubleshoot more easily and just roll back if necessary.
So, this is that in a nutshell. Alphabetically order all the test(s)/browser/browser.ini files in the directories we own. That should include...
- toolkit/components/messaging-system/schemas/TriggerActionSchemas/test/browser/browser.ini
- toolkit/components/messaging-system/schemas/SpecialMessageActionSchemas/test/browser/browser.ini
- browser/components/newtab/test/browser/browser.ini
- browser/components/newtab/test/browser/abouthomecache/browser.ini
I'm not sure if xpcshell manifests need to be alphabetic too, haven't edited one since this rule went into effect. Maybe wise to just alphabetize them anyway. The one in toolkit only has one entry so that can be ignored. I think that ultimately just leaves...
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Comment 2•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Updated•1 year ago
|
Comment 3•1 year ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit BugBot documentation.
Updated•7 months ago
|
I’m a new contributor, and I’ll be submitting a patch for this bug soon!
Reporter | ||
Comment 5•7 months ago
|
||
(In reply to Jason Ng from comment #4)
I’m a new contributor, and I’ll be submitting a patch for this bug soon!
Thanks, Jason! Just so you know, the test manifest locations have changed. They are now named browser.toml, and ours are in:
browser/components/aboutwelcome
browser/components/asrouter
toolkit/components/messaging-system
Comment 6•5 months ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit BugBot documentation.
Comment 7•5 months ago
|
||
I believe this bug can be closed as WONTFIX, as the test manifests for the directories in comment #5 are already in alphabetical order.
Reporter | ||
Comment 8•5 months ago
|
||
(In reply to Stephanie Cunnane [:scunnane] from comment #7)
I believe this bug can be closed as WONTFIX, as the test manifests for the directories in comment #5 are already in alphabetical order.
Great, thanks for confirming that Stephanie.
Updated•2 months ago
|
Description
•