[build] Don't build e2e tests and web test runner for release resources
This CL does two things:
1) It splits out the 'test/' directory and the web test resources
from 'devtools_frontend_resources'. This means just building
Chrome won't build DevTools' e2e tests or the web test runner.
We still include them in `devtools_all_files`, which should be
enough for the web tests upstream.
2) We no longer include the integration_test_runner.html and the
web test runner JS bundle in the DevTools release bundle.
As web tests host DevTools via apache, we don't actually have
to ship these files.
Note that unittests are still built as part of
'devtools_frontend_resources' as the TS indexer pulls them in.
We'll look into fixing that separately.
[email protected], [email protected]
Bug: 382387670
Change-Id: Ia4928453889de1a9b09dc880d9479fdc0419b375
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6448691
Reviewed-by: Philip Pfaffe <[email protected]>
Commit-Queue: Simon Zünd <[email protected]>
diff --git a/BUILD.gn b/BUILD.gn
index 134c536..526e35f 100644
--- a/BUILD.gn
+++ b/BUILD.gn
@@ -16,7 +16,6 @@
devtools_frontend_resources_deps = [
":favicon",
"front_end",
- "test",
]
group("devtools_all_files") {
@@ -25,7 +24,11 @@
# This enables us to test bots with whitespace changes.
"scripts/whitespaces.txt",
]
- data_deps = devtools_frontend_resources_deps
+
+ data_deps = devtools_frontend_resources_deps + [
+ "front_end:web_test_resources",
+ "test",
+ ]
public_deps = [ "front_end/ui/components/docs" ]
}
