Open
Bug 1265052
Opened 8 years ago
Updated 2 years ago
[meta] Move tests out of browser/base/content/test/general into test-subject-appropriate directories
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox48 | --- | affected |
People
(Reporter: Gijs, Unassigned)
References
Details
(Keywords: meta)
I almost titled this bug "browser/base/content/test/general is too ... full". Because really, that's the main problem. It takes ages to run, there's a lot of tests that can influence each other, it's hard to isolate a problem if tests do influence each other, it's hard to run tests relevant for the change you're making, it takes long on infra, if something breaks (cough bug 1253956 cough) everything gets mass-disabled... there are a lot of reasons to not want to have a directory with over 300 tests in. I'm about to make a start by moving 40-50 urlbar-related tests into their own directory (which I created a few weeks ago). We probably want some directory for tabbrowser (drag drop, pinned tabs, that kind of thing). Inevitably some tests will be hard to place (I just left something in general that tested text pasting in both the location and search bar). Either way, it's going to be useful to get general down to more manageable levels. Less than 200 would already be better, less than 100 would be quite good, and 50 or less would be ideal.
Updated•5 years ago
|
Summary: Move tests out of browser/base/content/test/general into test-subject-appropriate directories → [meta] Move tests out of browser/base/content/test/general into test-subject-appropriate directories
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•