Kir Kolyshkin
3fabb4d070
As runc binary grows in size over time (new features, more dependencies) some tests start to flake because of low memory limits. One such test is "runc run (cgroup v2 resources.unified override)"; it obviously fails because of 1M memory limit: > runc run failed: unable to start container process: container init was OOM-killed (memory limit too low?) Increase the limits 4x. Do the same for the "unified only" test. Fixes issue 5264. Reported-by: Kevin Berry <kpberry11@gmail.com> Reported-by: Ricardo Branco <rbranco@suse.de> Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
runc Integration Tests
Integration tests provide end-to-end testing of runc.
Note that integration tests do not replace unit tests.
As a rule of thumb, code should be tested thoroughly with unit tests. Integration tests on the other hand are meant to test a specific feature end to end.
Integration tests are written in bash using the bats (Bash Automated Testing System) framework. Please see bats documentation for more details.
Running integration tests
The easiest way to run integration tests is with Docker:
make integration
Alternatively, you can run integration tests directly on your host through make:
sudo make localintegration
Or you can just run them directly using bats
sudo bats tests/integration
To run a single test bucket:
make integration TESTPATH="/checkpoint.bats"
To run them on your host, you need to set up a development environment plus bats (Bash Automated Testing System).
For example:
cd ~/go/src/github.com
git clone https://github.com/bats-core/bats-core.git
cd bats-core
./install.sh /usr/local
Writing integration tests
Helper functions are provided in order to facilitate writing tests.
Please see existing tests for examples.