go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Fabricio Voznika 9e9fec3a09 Enable more VFS2 tests 
Updates #1487

PiperOrigin-RevId: 335516732
 		2020-10-05 15:54:36 -07:00
..
benchmarks Support creating protocol instances with Stack ref 2020-09-28 16:24:04 -07:00
cmd/test_app Simplify Docker test infrastructure. 2020-04-23 11:33:30 -07:00
e2e [testing] Use container address to talk to server running inside container. 2020-09-17 17:58:08 -07:00
fuse Fix kernfs unlinkat and rmdirat incorrect resolved path name 2020-09-17 21:07:12 +00:00
image [testing] Use container address to talk to server running inside container. 2020-09-17 17:58:08 -07:00
iptables Remove reference to deleted script 2020-10-05 15:49:14 -07:00
packetdrill Add bzl_library rules for .bzl files without one. 2020-08-06 12:10:49 -07:00
packetimpact Fix lingering of TCP socket in the initial state. 2020-09-28 16:39:12 -07:00
perf Run gentdents_benchmark with fewer files. 2020-09-03 10:54:01 -07:00
root Remove unused scripts. 2020-09-23 17:38:02 -07:00
runner Enable more VFS2 tests 2020-10-05 15:54:36 -07:00
runtimes Actually disable nodejs test parallel/test-fs-write-stream-double-close. 2020-10-02 11:51:17 -07:00
syscalls Fix kcov enabling and disabling procedures. 2020-10-03 09:26:25 -07:00
uds Standardize on tools directory. 2020-01-27 12:21:00 -08:00
util Internal change. 2020-10-05 13:17:19 -07:00
BUILD Standardize on tools directory. 2020-01-27 12:21:00 -08:00
README.md Remove unused scripts. 2020-09-23 17:38:02 -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:

make docker-tests

To run root tests, run:

make root-tests

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.