github.com/google/cadvisor@v0.49.1/docs/development/integration_testing.md (about)

     1  # Integration Testing cAdvisor 
     2  
     3  ## Docker-based tests
     4  
     5  The cAdvisor integration tests are run per-pr using [Github Actions](https://help.github.com/en/actions). Workflow configuration can be found at [.github/workflows/test.yml](.github/workflows/test.yml). Tests are executed in Docker containers run on MS Azure virtual machines.
     6  
     7  To run them locally Docker must be installed on your machine. Following command allows you to execute default suite of integration tests:
     8  
     9  ```
    10  make docker-test-integration
    11  ```
    12  
    13  Build scripts take care of building cAdvisor and integration tests, and executing them against running cAdvisor process.
    14  
    15  In order to run non-default tests suites (e.g. such that rely on third-party C libraries) you must source one of the files available at [build/config](build/config), e.g.:
    16  
    17  ```
    18  source build/config/libpfm4.sh && make docker-test-integration
    19  ```
    20  
    21  All the necessary packages will be installed, build flags will be applied and additional parameters will be passed to cAdvisor automatically. Configuration is performed using shell environment variables.
    22  
    23  ## VM-base tests (legacy)
    24  
    25  The cAdvisor integration tests are run per-pr using the [kubernetes node-e2e testing framework](https://github.com/kubernetes/community/blob/master/contributors/devel/e2e-node-tests.md) on GCE instances.  To make use of this framework, complete the setup of GCP described in the node-e2e testing framework, clone `k8s.io/kubernetes`, and from that repository run:
    26  ```
    27  $ make test-e2e-node TEST_SUITE=cadvisor REMOTE=true
    28  ```
    29  This will create a VM, build cadvisor, run integration tests on that VM, retrieve logs, and will clean up the test afterwards.  See the [node-e2e testing documentation](https://github.com/kubernetes/community/blob/master/contributors/devel/e2e-node-tests.md) for more running options.
    30  
    31  To simply run the tests against an existing cAdvisor:
    32  
    33  ```
    34  $ go test github.com/google/cadvisor/integration/tests/... -host=HOST -port=PORT
    35  ```
    36  
    37  Note that `HOST` and `PORT` default to `localhost` and `8080` respectively.
    38  Today We only support remote execution in Google Compute Engine since that is where we run our continuous builds.