go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/runsc/test
History
Samantha Sample 444a9d9e54 Publish Dockerfiles and test-runner binaries for running language tests. 
By following the directions in the README file, these Dockerfiles can be
built and used to run native language tests for their respective runtimes.

PiperOrigin-RevId: 260174430
 		2019-07-26 10:57:53 -07:00
..
image
…
integration test/integration: wait a background process 2019-07-16 15:06:17 -07:00
root
…
runtimes Publish Dockerfiles and test-runner binaries for running language tests. 2019-07-26 10:57:53 -07:00
testutil Avoid importing platforms from many source files 2019-07-03 22:51:26 -07:00
BUILD gvisor/kokoro: don't modify tests names in the BUILD file 2019-06-18 01:41:29 -07:00
README.md
…
build_defs.bzl
…
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