build_speed: Add unit tests and refactor benchmark script
Add comprehensive unit tests for the benchmark.py script to improve
robustness and prevent regressions. A PRESUBMIT.py file is also added to
run these tests automatically.
- Avoided testing private methods and some methods entirely (e.g.
_emulator) as they are more trouble than it's worth. Those can be
tested when running the entire script.
Additionally, refactor the script:
- Simplify emulator architecture detection.
- Add a --test flag to swap the target to chrome_public_test_apk.
- Since targets are per-run instead of per-test, this means that
whenever --test is used the caller is responsible for choosing the
appropriate suite.
- Add a --quiet flag to suppress summary output.
Also add hnakashima@ to help own this dir.
R=agrieve@chromium.org
Bug: 391374982
Change-Id: I8baf197745cb4734f2962a0862e27f703a97e1a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6930870
Auto-Submit: Peter Wen <wnwen@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1513174}
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.