Google Git
Sign in
chromium / chromium / src / components / reporting / 74f4644bf32b66e0ed0465645c6ca348e7b0653d
commit74f4644bf32b66e0ed0465645c6ca348e7b0653d[log] [tgz]
authorPaul Semel <paulsemel@chromium.org>Tue Jun 06 12:34:57 2023
committerCopybara-Service <copybara-worker@google.com>Tue Jun 06 12:39:34 2023
treedc1155a5d7a495b860cd5655e5d998c7b62b467e
parent6f8d5ffba345aae5e3b71e2a68a77f94d629a38f [diff]
DanglingPointer: annotate for unittests base+linux [3/N]

Bug: 1400059
AX-Relnotes: N/A.
Change-Id: Id59291f12370a6409cb0ab545e4f545fa1538675
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4577319
Owners-Override: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1153792}
NOKEYCHECK=True
GitOrigin-RevId: 5382b0d58a03334ba32a31bee2274d771461585e
1 file changed
tree: dc1155a5d7a495b860cd5655e5d998c7b62b467e
  1. client/
  2. compression/
  3. encryption/
  4. health/
  5. metrics/
  6. proto/
  7. resources/
  8. storage/
  9. storage_selector/
  10. util/
  11. DIR_METADATA
  12. OWNERS
  13. README.md
README.md

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:

  1. Run autoninja -C out/Default components_unittests to build the components unit test executable.

  2. 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.