Reland "Add browser test for FETCH_SUPPORT_PACKET remote command" This is a reland of commit 02a125795f6e3c9366db3cbaa6b95ce9120687d7 which got reverted on commit I274d362c7b02e1963c8c4784e9f303dcbf08d462 Fix by using PRId64 on formatter when printing int64_t Original change's description: > Add browser test for FETCH_SUPPORT_PACKET remote command > > Add browser test that uses RemoteCommandsServiceMixin to > FETCH_SUPPORT_PACKET command. For easier testing, add static > SetTargetDirForTesting() function to DeviceCommandFetchSupportPacketJob. > A temporary directory will be created and generated log file will be > written there for testing. Along with this addition remove > SetTargetDirForTesting() and GetExportedFilepathForTesting() functions. > Use `reporting::ReportingClient::TestEnvironment` as a test environment > to capture the enqueued events on the reporting pipeline. With this > addition, we don't need > DeviceCommandFetchSupportPacketJob::SetReportQueueForTesting() function > anymore so remove it. > Update the unit test according to these changes on > DeviceCommandFetchSupportPacketJob testing functions. > > Bug: b:313072234 > Change-Id: I6c018fa5f114fdd8c6b97d9833fe801befe3de2b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5153171 > Reviewed-by: Pavol Marko <pmarko@chromium.org> > Reviewed-by: Leonid Baraz <lbaraz@chromium.org> > Commit-Queue: Irem Uguz <iremuguz@google.com> > Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> > Cr-Commit-Position: refs/heads/main@{#1247068} Bug: b:313072234 Change-Id: Ib75414b97a94e5cba7ba0ed4023a066ccd74341e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5204345 Commit-Queue: Irem Uguz <iremuguz@google.com> Reviewed-by: Pavol Marko <pmarko@chromium.org> Cr-Commit-Position: refs/heads/main@{#1248662}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.