[monorail] Add lit-element, lit-html, pwa-helpers.

* lit-element: To replace Polymer. \o/
* lit-html: We will likely want to use some directives to customize templates.
* pwa-helpers: We can use connect-mixin to replace polymer-redux.


Bug: monorail:4839
Change-Id: I0450f3af98436937a84b512ccd455a4ebe81af1f
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/1566462
Reviewed-by: Tiffany Zhang <zhangtiff@chromium.org>
Commit-Queue: Dave Tu <dtu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#22408}
3 files changed
tree: e4ef2c8fc7de9857272a61205d2eb87f8b00650e
  1. .gitattributes
  2. .gitignore
  3. 3pp/
  5. DEPS
  9. README.md
  12. appengine/
  13. appengine_module/
  14. bootstrap/
  15. build/
  16. cipd/
  17. codereview.settings
  18. crdx/
  19. data/
  20. doc/
  21. docker/
  22. glyco/
  23. go/
  24. infra/
  25. navbar.md
  26. node/
  27. packages/
  28. recipes/
  29. run.py
  30. test.py
  31. test/
  32. utils/

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

  • run.py: wrapper script to run programs contained in subdirectories without having to deal with sys.path modifications.
  • test.py: 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.
  • infra/path_hacks: submodules of this modules give access to modules in the build/ repository. from infra.path_hacks.common import <stg> is actually getting <stg> from build/scripts/common.
  • 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 test.py

If you've added a new module, integrate your tests with test.py:

  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. More your *_test.py files to this directory.

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

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