187ad2c720
Bug: b:264399295 Change-Id: I4ef354aa7ba4cba0adfce5530f09509c4300eef1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4199209 Reviewed-by: Vignesh Shenvi <vshenvi@google.com> Commit-Queue: Leonid Baraz <lbaraz@chromium.org> Cr-Commit-Position: refs/heads/main@{#1102809}
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 Code shared between Chrome and Chrome OS.
- //chrome/browser/policy/messaging_layer Code that lives only in the browser, primary interfaces for reporting data such as ReportQueueImpl and ReportQueueConfiguration. Chrome OS:
- //platform2/missived Daemon for encryption and storage of reports.
If you'd like to begin using ERP within Chrome please check the comment in //components/reporting/client/report_queue_provider.h.
Run Unit Tests
To run the unit tests for this directory, after having configured Chromium's build environment:
-
Run
autoninja -C out/Default components_unitteststo 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 forStorageQueue, 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/reportingYou 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.