When I run a mochitest (without the --jsdebugger arg), I sometimes still want to open the Browser Toolbox after the fact. This requires jumping through hoops, because the following prefs are false by default: https://searchfox.org/mozilla-central/rev/465dbfe030dfec7756b9b523029e90d48dd5ecce/testing/mochitest/mochitest_options.py#708-713 So I need to manually go through steps to open it: https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox#Enabling_the_Browser_Toolbox. Then I run out of time and the mochitest times out before I get very far. Some workarounds available: 1) set up an [alias] in machrc like: ``` mochitest = mochitest --setpref devtools.chrome.enabled=true --setpref devtools.debugger.remote-enabled=true --setpref devtools.debugger.prompt-connection=false ``` 2) Always run `mochitest` with --jsdebugger or with the above --setpref calls But I assume this might be a common pain point, and suggest we should either: 1) remove the overrides in https://searchfox.org/mozilla-central/rev/465dbfe030dfec7756b9b523029e90d48dd5ecce/testing/profiles/perf/user.js#44-45 (they are true by default in We already do this for local builds at https://searchfox.org/mozilla-central/rev/465dbfe030dfec7756b9b523029e90d48dd5ecce/devtools/shared/preferences/devtools-shared.js#27) 2) Unconditionally set them to true for mochitest only at https://searchfox.org/mozilla-central/rev/465dbfe030dfec7756b9b523029e90d48dd5ecce/testing/mochitest/mochitest_options.py#708-713.
Bug 1522921 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When I run a mochitest (without the --jsdebugger arg), I sometimes still want to open the Browser Toolbox after the fact. This requires jumping through hoops, because the following prefs are false by default: https://searchfox.org/mozilla-central/rev/465dbfe030dfec7756b9b523029e90d48dd5ecce/testing/mochitest/mochitest_options.py#708-713 So I need to manually go through steps to open it: https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox#Enabling_the_Browser_Toolbox. Then I run out of time and the mochitest times out before I get very far. Some workarounds available: 1) set up an [alias] in machrc like: ``` mochitest = mochitest --setpref devtools.chrome.enabled=true --setpref devtools.debugger.remote-enabled=true --setpref devtools.debugger.prompt-connection=false ``` 2) Always run `mochitest` with --jsdebugger or with the above --setpref calls But I assume this might be a common pain point, and suggest we should either: 1) remove the overrides in https://searchfox.org/mozilla-central/rev/465dbfe030dfec7756b9b523029e90d48dd5ecce/testing/profiles/perf/user.js#44-45. We already do this for local builds at https://searchfox.org/mozilla-central/rev/465dbfe030dfec7756b9b523029e90d48dd5ecce/devtools/shared/preferences/devtools-shared.js#27) 2) Unconditionally set them to true for mochitest only at https://searchfox.org/mozilla-central/rev/465dbfe030dfec7756b9b523029e90d48dd5ecce/testing/mochitest/mochitest_options.py#708-713.