Reland "[chrome-test-health] API calls for incremental and absolute coverage trends"

This is a reland of commit d1132414409217e35e11aa2b84a3be1a95aa0610

Original change's description:
> [chrome-test-health] API calls for incremental and absolute coverage trends
> Added the frontend calls for APIs needed to fetch data for absolute and incremental coverage percentage trends over days.
> This CL also includes couple of lint fixes too.
> Bug: 1471660
> Change-Id: I88a54d9aad2bd0733633956a37d687bedf1393dc
> Reviewed-on:
> Reviewed-by: Struan Shrimpton <>
> Commit-Queue: Vidit Chitkara <>
> Cr-Commit-Position: refs/heads/main@{#61621}

Bug: 1471660
Change-Id: I1be40a89115b8ebadab9ee7841d61756d45bc5f6
Reviewed-by: Struan Shrimpton <>
Commit-Queue: Vidit Chitkara <>
Cr-Commit-Position: refs/heads/main@{#61631}
4 files changed
tree: 1ed758f1ca17dbb1ec042857699c7579081897e9
  1. 3pp/
  2. appengine/
  3. appengine_module/
  4. bootstrap/
  5. build/
  6. chromeperf/
  7. crdx/
  8. doc/
  9. docker/
  10. go/
  11. infra/
  12. node/
  13. packages/
  14. python_pb2/
  15. rbe/
  16. recipes/
  17. test/
  18. utils/
  19. .gitallowed
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .style.yapf
  24. .vpython
  25. .vpython3
  26. .yapfignore
  27. codereview.settings
  29. DEPS
  33. OWNERS

infra.git repository

Welcome to the Chrome Infra repository!

Wondering where to start? Check out General Chrome Infrastructure documentation. In particular, to check out this repo and the rest of the infrastructure code, follow the instructions here. The rest of this page is specific to this repo.

Entry points

  • wrapper script to run programs contained in subdirectories without having to deal with sys.path modifications.
  • multi-purpose script to run tests.
  • packages/infra_libs/: generally useful functions and classes
  • infra/services/: standalone programs intended to be run as daemons.
  • infra/tools: command-line tools, intended to be run by developers.
  • appengine/: many Chrome-infra-managed AppEngine applications.
  • infra/experimental: for, well, experimental stuff. Once they are stabilized and reviewed, they should be moved in a more permanent place.

Miscellaneous technical stuff

  • bootstrap/: utilities to set up a proper Python virtual environment.
  • utils/: purpose? utils?
  • Need to bump infra/deployed to pick up changes?
    • git push origin <updated hash>:deployed
    • mail chrome-troopers@, include:
      • previously deployed hash (for quick rollback)
      • the hash you just pushed
      • the list of CLs that made this push necessary
      • the output of the git push command

Integrating tests with

If you've added a new module, run your tests with

  1. Create a .coveragerc file in the root directory of the module you want to test. Take a look at another .coveragerc to see what to include in that.
  2. Create a “test” directory in the root directory of the module you want to test. Move your * files to this directory.

Double-check that your tests are getting picked up when you want them to be: ./ test <path-to-package>.

Tests still not getting picked up by Double-check to make sure you have files in each directory of your module so Python recognizes it as a package.


The preferred style is PEP8 with two-space indent; that is, the Chromium Python style, except functions use lowercase_with_underscores. Use yapf (git cl format) to autoformat new code.