Fix preference handling of enforce_gecko_prefs() and do a safe shutdown
Categories
(Testing :: Marionette Client and Harness, defect, P3)
Tracking
(Not tracked)
People
(Reporter: whimboo, Unassigned)
References
Details
(Keywords: pi-marionette-client)
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Comment 2•9 years ago
|
||
Reporter | ||
Comment 4•8 years ago
|
||
Updated•7 years ago
|
Comment 5•6 years ago
|
||
Another use case for you, this time from bug 1550718
I tried to use enforce_gecko_prefs()
in a test to check behaviour that happens as a result of the preferences being set. This might not be a good fit, but it would be nice to have a chance to force the prefs without being forced to restart the instance.
Also, the interaction with prefs already set is unclear. If I set the prefs on the instance manually, enforce_gecko_prefs
might no-op when I ask it to enforce that the set prefs persist across restarts. However, if I then manually restart the instance the prefs aren't actually enforced. Perhaps enforce_gecko_prefs
should check against the dict it is using to enforce the prefs in addition to checking the prefs in the currently-running instance.
Updated•3 years ago
|
Updated•2 years ago
|
Reporter | ||
Updated•2 years ago
|
Comment 6•10 months ago
|
||
In Bug 1899346, I need to test some browser startup/initialization behavior with different pref states. The pref wasn't defined at all, one pref was false, another true at startup etc. Because I needed to ensure startup happened so the initialization code under test for sure ran (to avoid false positives), I found I was not able to use enforce_gecko_prefs()
. This might be a niche case, but hopefully its a useful datapoint.
Description
•