Stop hardcoding cert fingerprints in webview_login_browsertest.cc
Change tests in webview_login_browsertest.cc to calculate the expected fingerprint dynamically at runtime, rather than hardcode it as hex strings in the test code. This simplifies the tests maintenance and also makes them more readable, by replacing magic hex blobs with human-readable cert file names. The main purpose of these tests is anyway the login-screen behavior, and not the cert fingerprint calculation, therefore it's presumably not very important to have "golden" data hardcoded in these tests. Bug: 905994 Change-Id: Ie8ee63d6a54087fa77ae64e7c487b19b0c884be9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2426705Reviewed-by:Pavol Marko <pmarko@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#810576}
Showing
Please register or sign in to comment