gvisor/runsc/test
Kevin Krakauer a81111d544 Fix problem where crictl tests would signal both error and done channels
PiperOrigin-RevId: 220372291
Change-Id: I054ba56a23c402c7244b476d7d6fe72084942a0e
2018-11-06 16:18:13 -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 First crictl integration tests. 2018-11-01 18:29:07 -07:00
testutil Fix problem where crictl tests would signal both error and done channels 2018-11-06 16:18:13 -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