Testing safe mode

Ehsan Akhgari ehsan.akhgari at gmail.com
Fri Dec 23 20:40:36 UTC 2016

On Fri, Dec 23, 2016 at 3:37 PM, Lawrence Mandel <lmandel at mozilla.com>

> That does seem bad as safe mode is our mitigation strategy for a number of
> issues.
> What tests do we need to execute for safe mode to prove that the env is
> correct and functional? Are there existing tests that we can use in the
> safe mode configuration?

Is there any reason we should pick a subset?  I think we should run all of
our tests under safe-mode (and skip the ones which are testing the stuff
that won't work in safe mode, and obvious things such as extension tests).

Of course, I don't think we should run them per check-in necessarily, but
with a slower cadence, similar to our PGO builds.

> Lawrence
> On Fri, Dec 23, 2016 at 3:34 PM, Ehsan Akhgari <ehsan.akhgari at gmail.com>
> wrote:
>> About 3 weeks ago I heavily broke basic browsing safe mode on Nightly
>> (sorry about that!) and today we got a bug report that led to investigation
>> (bug 1325651).
>> Have we ever thought about running automated tests on safe mode, at least
>> periodically?  We currently don't even run automatic smoketests to make
>> sure you can load web pages in safe mode, which seems bad for a mode that
>> is supposed to be working with a higher probability than normal mode.
>> Thanks,
>> --
>> Ehsan
>> _______________________________________________
>> firefox-dev mailing list
>> firefox-dev at mozilla.org
>> https://mail.mozilla.org/listinfo/firefox-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/firefox-dev/attachments/20161223/afe480e8/attachment.html>

More information about the firefox-dev mailing list