go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/runsc/test
History
Andrei Vagin fff21b99e4 kokoro: run tests with a default docker container runtime 
We want to know that our environment set up properly
and docker tests pass with a native runtime.

PiperOrigin-RevId: 248229294
Change-Id: I06c221e5eeed6e01bdd1aa935333c57e8eadc498
 		2019-05-14 16:01:50 -07:00
..
image gvisor/runsc/tests: set timeout for http.Get() 2019-05-13 00:50:44 -07:00
integration gvisor/runsc/tests: set timeout for http.Get() 2019-05-13 00:50:44 -07:00
root Change copyright notice to "The gVisor Authors" 2019-04-29 14:26:23 -07:00
testutil kokoro: run tests with a default docker container runtime 2019-05-14 16:01:50 -07:00
README.md netstack: reduce MSS from SYN to account tcp options 2019-03-19 17:33:20 -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