go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Haibo e0c84f284c test/syscall: Remove duplicated gtest/gtest.h. 
Signed-off-by: Haibo Xu <haibo.xu@arm.com>
Change-Id: I05a7ec69b98b88931ba4a8adb3e8a7b822006001
COPYBARA_INTEGRATE_REVIEW=https://github.com/google/gvisor/pull/1023 from xiaobo55x:syscall_test d44a8b1f827ed4081997af96cd58ba7449e0a9e1
PiperOrigin-RevId: 276740442
 		2019-10-25 12:40:36 -07:00
..
e2e Add more instructions to test/README.md 2019-10-18 16:18:52 -07:00
image Impose order on test scripts. 2019-09-03 22:02:43 -07:00
root Fix early deletion of rootDir 2019-10-24 16:36:54 -07:00
runtimes Add blacklists for remaining runtime tests, and test that they parse correctly. 2019-10-09 11:22:53 -07:00
syscalls test/syscall: Remove duplicated gtest/gtest.h. 2019-10-25 12:40:36 -07:00
uds Cleanup host UDS support 2019-10-18 15:33:03 -07:00
util Handle AT_EMPTY_PATH flag in execveat. 2019-10-23 22:23:05 -07:00
BUILD Bump Bazel to v0.28.0 2019-08-13 11:21:55 -07:00
README.md Add more instructions to test/README.md 2019-10-18 16:18:52 -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.

  • syscalls: system call tests use a local runner, and do not require additional configuration in the machine.
  • integration: defines integration tests that uses docker run to test functionality.
  • image: basic end to end test for popular images. These require the same setup as integration tests.
  • root: tests that require to be run as root. These require the same setup as integration tests.
  • util: utilities library to support the tests.

For the above noted cases, the relevant runtime must be installed via runsc install before running. Just note that they require specific configuration to work. This is handled automatically by the test scripts in the scripts directory and they can be used to run tests locally on your machine. They are also used to run these tests in kokoro.

Example:

To run image and integration tests, run:

./scripts/docker_test.sh

To run root tests, run:

./scripts/root_test.sh

There are a few other interesting variations for image and integration tests:

  • overlay: sets writable overlay inside the sentry
  • hostnet: configures host network pass-thru, instead of netstack
  • kvm: runsc the test using the KVM platform, instead of ptrace

The test will build runsc, configure it with your local docker, restart dockerd, and run tests. The location for runsc logs is printed to the output.