Misc fixes for test scripts (minor changes)

- Using python protos requires more dependencies in vpython files (both changes went in at the same time)
- Missing return in ./run_tests.py (oops)
- Missing an __init__.py file (stale pyc was laying around locally)
- Missing import after moving code to a different file
- Stale `self` reference after refactoring method
- Install grpc-google-iam-admin-v1 instead of gapic- (grpc was pulled as a dependency to gapic)

Intermittent failures:
- Don't generate passwords that start with `/`, they're interpreted as a flag by `net user`:
  > The option /K~,A_QAZOZEWR%);DHFKT#~G#<J*@E= is unknown.
- Increase RDS Test timeout - I've seen the 2008 AD client take just over 60mins to finish (30mins waiting for the AD, 30mins to join/setup RDS), which fails the test. Increased the timeout to 90mins.

Change-Id: I1b8a198927fd17758eae27761a71b95dbdd7ea56
Reviewed-on: https://chromium-review.googlesource.com/c/1392509
Reviewed-by: Fei Ling <feiling@chromium.org>
9 files changed
tree: e7b0c3e1c469f71b930bc130cbf6fddc667e2839
  1. .gitignore
  2. .gitmodules
  3. .style.yapf
  4. .vpython
  5. CODE_OF_CONDUCT.md
  6. CONTRIBUTING.md
  7. Gopkg.lock
  8. Gopkg.toml
  9. LICENSE
  10. OWNERS
  11. PRESUBMIT.py
  12. README.md
  13. VERSION
  14. build.py
  15. build/
  16. codereview.settings
  17. docs/
  18. examples/
  19. go/
  20. infra/
  21. navbar.md
  22. resources/
  23. run_tests.py
  24. schema/
  25. scripts/
  26. test.py
  27. test/
README.md

Chrome Enterprise Lab

Chrome Enterprise Lab is an inaccurately named set of tools for building enterprise labs quickly and easily. The labs so built can be used for system level end-to-end testing of Google Chrome/Chromium.

Have a peek at the Design document.

Also have a peek at the Code of Conduct.

Most of the code is in Go. See Guide to code to get a head start on the code in this repository.

Building

Prerequisites

  • Go: Download Go from the Go download page. This project requires Go 1.9.4 or later. The build will fail with prior versions.

  • Depot Tools: Used for managing the checkout and the contributor workflow.

  • Protocol Buffers Compiler: Protocol buffers are used extensively for wranging all the data that needs to be shuttled around. Can be installed automatically via ./build.py deps --install.

  • Dep : Used for Go depedency management. This can be installed automatically by running ./build.py deps --install from the root of the source tree.

  • Go support for Protocol Buffers : This can be installed automatically by running ./build.py deps --install from the root of the source tree.

Get The Source

There are two ways to get the source. One is to use managed deps, and the other is to use plain go get. The latter workflow doesn't quite work yet due to this repository not being integrated with go.chromium.org. So this page only mentions the managed dependency workflow.

  1. Clone this repository:

    Assumes that $GOPATH is a single path and not a : delimited list.

    mkdir -p ${GOPATH}/src/chromium.googlesource.com/enterprise
    cd ${GOPATH}/src/chromium.googlesource.com/enterprise
    git clone https://chromium.googlesource.com/enterprise/cel
    cd cel
    
  2. Get the dependencies:

    python build.py deps --install
    

Build It

  1. Use the build script:

    python build.py build
    
  2. Also make sure the tests pass.

    python build.py test
    

Contributing

See CONTRIBUTING.