[Android] Fix argument order for assertEquals calls
assertEquals accepts an expected value as the first argument and an actual value as the second. This CL fixes some tests that were using the reversed order. Bug: None Change-Id: I158277a01d6146ef46b1b2fc97af04c7dcd7a563 Reviewed-on: https://chromium-review.googlesource.com/1008002Reviewed-by:Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Cr-Commit-Position: refs/heads/master@{#553486}
Showing
Please register or sign in to comment