go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Eyal Soha a2925a079f Run failing packetimpact test and expect failure. 
This will make it easier to notice if a code change causes an existing test to
pass.

PiperOrigin-RevId: 308057978
 		2020-04-23 08:36:19 -07:00
..
e2e Fix race in TestRunEnvHasHome 2020-03-25 15:58:45 -07:00
image Add notes to relevant tests. 2020-02-05 22:46:35 -08:00
iptables Support owner matching for iptables. 2020-03-26 12:21:24 -07:00
packetdrill Convert tcp_user_timeout test from packetdrill to packetimpact. 2020-04-19 20:49:06 -07:00
packetimpact Run failing packetimpact test and expect failure. 2020-04-23 08:36:19 -07:00
perf Deflake //third_party/gvisor/test/perf:getdents_benchmark_runsc_ptrace 2020-04-03 12:29:03 -07:00
root Add a functional vm_test for root_test. 2020-04-20 15:48:27 -07:00
runner Internal change. 2020-04-21 09:44:00 -07:00
runtimes Fix all printf formatting errors. 2020-04-08 10:14:34 -07:00
syscalls tcp: handle listen after shutdown properly 2020-04-22 14:17:11 -07:00
uds Standardize on tools directory. 2020-01-27 12:21:00 -08:00
util Add missing newline 2020-04-03 11:38:37 -07:00
BUILD Standardize on tools directory. 2020-01-27 12:21:00 -08:00
README.md
…

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.