Add more PASSWORDS integration tests
They verify some otherwise-untested but privacy-sensitive requirements of what is being sent on the wire, where most (without custom passphrase) or all (with custom passphrase) proto fields should be encrypted. The actual verification is done using the state in the fake server, which is assumed to store committed content without pruning. This holds true today and is unlikely to change in the future. Bug: 856941,870624 Change-Id: I9198ca69c53d55a80f4b2a0c55cd5265e57741aa Reviewed-on: https://chromium-review.googlesource.com/c/1290809 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#601126}
Showing
Please register or sign in to comment