Remove most base/files/file_util.h includes from headers Most headers do not need to include file_util.h. Instead, either include file_path.h, or forward declare base::FilePath. Then do IWYU to fix the build. Also forward declare base::FileEnumerator in one case. Change-Id: I99193a8c5ee309fdba56b6f70cc753dc08983840 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7099339 Owners-Override: Kyle Charbonneau <kylechar@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by: Kyle Charbonneau <kylechar@chromium.org> Cr-Commit-Position: refs/heads/main@{#1538232} NOKEYCHECK=True GitOrigin-RevId: adb7e791ecf552ea3d97bf76aeca15c178241ca2
The Encrypted Reporting Pipeline (ERP) provides a universal method for upload of data for enterprise customers.
The code structure looks like this:
Chrome:
//components/reporting //chrome/browser/policy/messaging_layer ReportQueueImpl and ReportQueueConfiguration.ChromeOS:
//platform2/missived If you'd like to begin using ERP within Chrome please check the comment in //components/reporting/client/report_queue_provider.h.
To run the unit tests for this directory, after having configured Chromium's build environment:
Run autoninja -C out/Default components_unittests to build the components unit test executable.
Then, run out/Default/components_unittests --gtest_filter='<target tests>' to run relevant tests. Here, <target tests> is a wildcard pattern (refer to the document of gtest for more details). For example, to run all tests for StorageQueue, run
$ out/Default/components_unittests --gtest_filter='*/StorageQueueTest.*'
For another example, to run all tests in this directory, run
$ tools/autotest.py -C out/Default --run_all components/reporting
You can also append a filter such as --gtest_filter='*/StorageQueueTest.*' to the line above.
Another useful flag for dealing with flaky tests is --gtest_repeat=, which repeats tests for multiple times.
For more gtest features, check out the gtest document.