Avoid rule ranges in MatchResultTest
Instead of relying on calls to UaRules/UserRules/AuthorRules/AllRules, just check the origin at each vector index directly. This prepares for the removal of the rule ranges in a subsequent CL. Change-Id: I86f57ca1c2f04619db99f7cd1c62345b8f0f262a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310675 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#791174}
Showing
Please register or sign in to comment