Closed
Bug 1608831
Opened 4 years ago
Closed 4 years ago
Give geckoview-junit its own profile configuration in automation
Categories
(GeckoView :: General, defect, P2)
Tracking
(firefox74 fixed)
RESOLVED
FIXED
mozilla74
| Tracking | Status | |
|---|---|---|
| firefox74 | --- | fixed |
People
(Reporter: snorp, Assigned: gbrown)
Details
(Whiteboard: dev-prod-2020)
Attachments
(1 file)
Right now we share the one used by other unit testing frameworks (mochitest), and some of the prefs are not configured correctly. We end up needing to clobber them in the tests themselves, and that's bad.
|
Assignee | |
Updated•4 years ago
|
Assignee: nobody → gbrown
Priority: -- → P2
|
|
Assignee | |
Comment 1•4 years ago
|
||
Historically, mochitest and geckoview-junit tests have used the same profile.
This patch splits out a separate profile type for geckoview-junit, with exactly
the same content for now; the geckoview team can follow-up with whatever
profile changes are required for junit.
Pushed by gbrown@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0728e1e38e3f Use a distinct profile category for geckoview-junit tests; r=snorp
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox74:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
|
|
Assignee | |
Updated•4 years ago
|
Whiteboard: dev-prod-2020
You need to log in
before you can comment on or make changes to this bug.
Description
•