go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Kevin Krakauer 6b085ba477 setgid: skip tests when we can't find usable GIDs 
PiperOrigin-RevId: 365092320
 		2021-03-25 12:00:24 -07:00
..
benchmarks Address post submit comments for fs benchmarks. 2021-03-18 12:14:27 -07:00
cmd/test_app Fix simple mistakes identified by goreportcard. 2021-01-12 12:38:22 -08:00
e2e Call kernfs.syntheticDir.InitRefs() on creation. 2021-02-04 11:47:52 -08:00
fsstress Fix fsstress argument name 2021-01-21 13:20:52 -08:00
fuse fusefs: Implement default_permissions and allow_other mount options. 2021-03-11 17:59:13 -08:00
image [testing] Use container address to talk to server running inside container. 2020-09-17 17:58:08 -07:00
iptables [op] Replace syscall package usage with golang.org/x/sys/unix in test/. 2021-03-06 09:54:09 -08:00
kubernetes
…
packetdrill Refactor the Makefile to avoid recursive Make. 2020-12-09 15:53:23 -08:00
packetimpact Fix logs for packetimpact tests cleanup 2021-03-22 14:10:00 -07:00
perf Run shards in a single sandbox 2021-03-08 14:48:16 -08:00
root Switch uses of os.Getenv that check for empty string to os.LookupEnv. 2021-01-13 15:15:20 -08:00
runner Fix invalid interface conversion in runner 2021-03-09 20:12:20 -08:00
runtimes [op] Replace syscall package usage with golang.org/x/sys/unix in test/. 2021-03-06 09:54:09 -08:00
syscalls setgid: skip tests when we can't find usable GIDs 2021-03-25 12:00:24 -07:00
uds [op] Replace syscall package usage with golang.org/x/sys/unix in test/. 2021-03-06 09:54:09 -08:00
util Assign controlling terminal when tty is opened and support NOCTTY 2021-02-11 11:09:22 -08:00
BUILD
…
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:

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.