go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/runsc/test
History
Michael Pratt 5b41ba5d0e Fix various spelling issues in the documentation 
Addresses obvious typos, in the documentation only.

COPYBARA_INTEGRATE_REVIEW=https://github.com/google/gvisor/pull/443 from Pixep:fix/documentation-spelling 4d0688164eafaf0b3010e5f4824b35d1e7176d65
PiperOrigin-RevId: 255477779
 		2019-06-27 14:25:50 -07:00
..
image gvisor/kokoro: don't modify tests names in the BUILD file 2019-06-18 01:41:29 -07:00
integration gvisor/kokoro: don't modify tests names in the BUILD file 2019-06-18 01:41:29 -07:00
root Update canonical repository. 2019-06-13 16:50:15 -07:00
testutil Fix various spelling issues in the documentation 2019-06-27 14:25:50 -07:00
BUILD gvisor/kokoro: don't modify tests names in the BUILD file 2019-06-18 01:41:29 -07:00
README.md netstack: reduce MSS from SYN to account tcp options 2019-03-19 17:33:20 -07:00
build_defs.bzl gvisor/kokoro: don't modify tests names in the BUILD file 2019-06-18 01:41:29 -07:00
install.sh Fix runsc restore to be compatible with docker start --checkpoint ... 2019-05-03 21:41:45 -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