Change string to string_view to avoid an unnecessary copy. `.substr()` on a string_view returns another string_view instead of creating a new string. Bug: 501076278 Change-Id: Iadaa8daf02426362f4b3730d043f9504143cb106 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7771167 Reviewed-by: Vignesh Shenvi <vshenvi@google.com> Reviewed-by: Dominique Fauteux-Chapleau <domfc@chromium.org> Commit-Queue: Jeffrey Yu <yuje@chromium.org> Auto-Submit: Jeffrey Yu <yuje@chromium.org> Cr-Commit-Position: refs/heads/main@{#1617631} NOKEYCHECK=True GitOrigin-RevId: 3b0895470229e10558a05baf2e3dcaf640cfb9ba
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.