1378171 - Test which JS modules and components are loaded during content process startup

Status: RESOLVED FIXED

(Firefox :: General, enhancement, P1)

Description

[Florian Quèze [:florian]]

Similarly to the browser_startup.js test landed in bug 1358798, we should test what scripts get loaded when starting a content process.

Comment 1

[Florian Quèze [:florian]]

Attachment: Patch

https://treeherder.mozilla.org/#/jobs?repo=try&revision=460bd3e6ffb249c4ad6e679aa1ba0ce840a3d14b

Comment 2

[Florian Quèze [:florian]]

Attachment: Patch v2

Fixed the eslint failure by enabling the frame-script environment inside the framescript, and disabled on !e10s where this doesn't make sense (as we can't create a new process so the test sees modules loaded by previous tests...).

Comment 3

[Mike Conley (:mconley) (:⚙️)]

Comment on attachment 8883386 [details] [diff] [review]
Patch v2

Review of attachment 8883386 [details] [diff] [review]:
-----------------------------------------------------------------

Thanks!

::: browser/base/content/test/performance/browser_startup_content.js
@@ +40,5 @@
> +  let tab = await BrowserTestUtils.openNewForegroundTab({gBrowser,
> +                                                         forceNewProcess: true});
> +
> +  let mm = gBrowser.selectedBrowser.messageManager;
> +  let promise = new Promise(resolve => {

Alternatively, waitForMessage from BrowserTestUtils could be modified to resolve with the message data. I wouldn't block on that though. http://searchfox.org/mozilla-central/rev/a3a739de04ee6134c11546568a33dbb6a6a29907/testing/mochitest/BrowserTestUtils/BrowserTestUtils.jsm#908

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/2d7a625e8c99
add a test preventing us from loading scripts unintentionally during content process startup, r=mconley.

Comment 5

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/2d7a625e8c99