gvisor/runsc/test
Andrei Vagin 5f08f8fd81 Don't bind-mount runsc into a sandbox mntns
PiperOrigin-RevId: 230437407
Change-Id: Id9d8ceeb018aad2fe317407c78c6ee0f4b47aa2b
2019-01-22 16:46:42 -08:00
..
image Re-enable TestPythonHello now that ptrace seccomp issue is resolved. 2018-10-24 23:07:35 -07:00
integration Prevent internal tmpfs mount to override files in /tmp 2019-01-16 12:48:32 -08:00
root Don't bind-mount runsc into a sandbox mntns 2019-01-22 16:46:42 -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