go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Fabricio Voznika 010b093258 Bring back to life features lost in recent refactor 
- Sandbox logs are generated when running tests
- Kokoro uploads the sandbox logs
- Supports multiple parallel runs
- Revive script to install locally built runsc with docker

PiperOrigin-RevId: 269337274
 		2019-09-16 08:17:00 -07:00
..
e2e Impose order on test scripts. 2019-09-03 22:02:43 -07:00
image Impose order on test scripts. 2019-09-03 22:02:43 -07:00
root Bring back to life features lost in recent refactor 2019-09-16 08:17:00 -07:00
runtimes Impose order on test scripts. 2019-09-03 22:02:43 -07:00
syscalls gvisor: return ENOTDIR from the unlink syscall 2019-09-13 21:44:57 -07:00
util Load C++ rules from @rules_cc 2019-09-06 11:29:00 -07:00
BUILD Bump Bazel to v0.28.0 2019-08-13 11:21:55 -07:00
README.md Impose order on test scripts. 2019-09-03 22:02:43 -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.
  • util: utilities library to support the tests.

For the above noted cases, the relevant runtime must be installed via runsc install before running. This is handled automatically by the test scripts in the kokoro directory.