Chrome Release Bot (LUCI) 4762b62e7d Publish DEPS for 106.0.5249.13 | vor 1 Jahr | |
---|---|---|
.. | ||
client | vor 1 Jahr | |
compression | vor 1 Jahr | |
encryption | vor 1 Jahr | |
health | vor 1 Jahr | |
metrics | vor 1 Jahr | |
proto | vor 1 Jahr | |
resources | vor 1 Jahr | |
storage | vor 1 Jahr | |
storage_selector | vor 1 Jahr | |
util | vor 1 Jahr | |
DIR_METADATA | vor 1 Jahr | |
OWNERS | vor 1 Jahr | |
README.md | vor 1 Jahr |
The Encrypted Reporting Pipeline (ERP) provides a universal method for upload of data for enterprise customers.
The code structure looks like this: Chrome:
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.