commit | 9fddb128a42d32f09dde55fe9f3629a68417e0e3 | [log] [tgz] |
---|---|---|
author | Matt Menke <mmenke@chromium.org> | Fri Feb 28 20:23:32 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 28 20:23:32 2025 |
tree | 5466db02769c89ebb87861953347982bd3f0b5aa | |
parent | 1a782a287d272ef1fdaca2ade5b0225249bac9a7 [diff] |
[Protected Audience] Add trusted signals KVv2 instrumentation tests. In particular, extend auction-network-events-handler.js to run tests both for the legacy KVv1 case and the new KVv2 case, which are distinguished by pass in a coordinator to Protected Audience APIs. Trusted signals version 2 requests require configuring a global fake coordinator URL to set up an extra layer of encryption of top of HTTPS. So this CL also adds a new virtual test suite to set a coordinator. Since the tests only monitor network requests, there's no need to correctly set up KVv2 encryption (that will be covered by WPT tests) - only need to set up a coordinator in the virtual test suite and have it set up a valid JSON key file. Bug: 379843989 Change-Id: I8a8ff40063fded770edfa9b7c04078845f0e4b50 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6310081 Reviewed-by: Mason Freed <masonf@chromium.org> Reviewed-by: Maks Orlovich <morlovich@chromium.org> Commit-Queue: mmenke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/main@{#1426510}
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.