gvisor/runsc/test
Michael Pratt b62591e6a8 Expose internal testing flag
Never to used outside of runsc tests!

PiperOrigin-RevId: 225919013
Change-Id: Ib3b14aa2a2564b5246fb3f8933d95e01027ed186
2018-12-17 17:35:06 -08:00
..
image Re-enable TestPythonHello now that ptrace seccomp issue is resolved. 2018-10-24 23:07:35 -07:00
integration Track paths and provide a rename hook. 2018-10-23 00:20:15 -07:00
root Fix crictl tests. 2018-11-28 10:10:13 -08:00
testutil Expose internal testing flag 2018-12-17 17:35:06 -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