gvisor/runsc/test
Fabricio Voznika 52a2abfca4 Fix cgroup when path is relative
This can happen when 'docker run --cgroup-parent=' flag is set.

PiperOrigin-RevId: 235645559
Change-Id: Ieea3ae66939abadab621053551bf7d62d412e7ee
2019-02-25 19:21:47 -08:00
..
image Remove license comments 2019-01-31 11:12:53 -08:00
integration Remove license comments 2019-01-31 11:12:53 -08:00
root Fix cgroup when path is relative 2019-02-25 19:21:47 -08:00
testutil Fix cgroup when path is relative 2019-02-25 19:21:47 -08:00
README.md Fix sandbox chroot 2018-10-03 20:44:20 -07:00
install.sh Use correct company name in copyright header 2018-10-19 16:35:11 -07:00

README.md

Tests

The tests defined under this path are verifying functionality beyond what unit tests can cover, e.g. integration and end to end tests. Due to their nature, they may need extra setup in the test machine and extra configuration to run.

  • integration: defines integration tests that uses docker run to test functionality.
  • image: basic end to end test for popular images.
  • root: tests that require to be run as root.
  • testutil: utilities library to support the tests.

The following setup steps are required in order to run these tests:

 `./runsc/test/install.sh [--runtime <name>]`

The tests expect the runtime name to be provided in the RUNSC_RUNTIME environment variable (default: runsc-test). To run the tests execute:

bazel test --test_env=RUNSC_RUNTIME=runsc-test \
  //runsc/test/image:image_test \
  //runsc/test/integration:integration_test