commit 177647450f23ecede6865777b7a3ab19b87c0c4c
author Devlin Cronin <rdevlin.cronin@chromium.org> Thu Dec 23 01:54:18 2021
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Thu Dec 23 01:54:18 2021
tree e2e094491455b49da134a54bd08602f684db8ef5
parent 2a2d43bf1c27915fe8f93ed1054dd229fbed0736

[Service Workers] Add a test-only method to execute javascript

There are times that a C++ test needs to coordinate code execution
between the C++ and running JS code. For frame-based contexts, we
can use EvalJs() and ExecuteScript*() methods from content
browser_test_utils; however, these require a RenderFrameHost or
WebContents to target.

Introduce a new method to allow executing javascript in the context
of a running worker. This method is exposed on ServiceWorkerContext
(for public access outside the //content layer) and in
ServiceWorkerVersion (internally in the content layer), and then
funnels to a mojo message on the ServiceWorker mojom interface. This
is somewhat inspired by and analogous to the RenderFrame equivalents
(where the method is exposed on RenderFrameHost and pipes to the
Frame mojom interface).

The result of the running script is serialized to a base::Value, and
an error string is populated if an exception is reached in executing
the script.

Also add an extension usage of this, allowing execution of script in
an extensions background service worker.

Add browsertests for both the extension-specific functionality and the
new method on ServiceWorkerVersion.

Bug: 1280077
Change-Id: I03939c5e0bb99c23ed348ee1b9b1bfaeaa4d0942
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3342489
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#953723}