Kir Kolyshkin
f9a9a36fa8
Since switching to Go 1.25 in go.mod, the "detect fd leaks" test fails like this: > not ok 57 runc create[detect fd leak as comprehensively as possible] > # (in test file tests/integration/create.bats, line 76) > # `[ "$violation_found" -eq 0 ]' failed > ... > # Violation: FD 9 -> '/system.slice/runc-test_busybox.scope/cpu.cfs_quota_us' > # Violation: FD 10 -> '/system.slice/runc-test_busybox.scope/cpu.cfs_period_us' > ... This happens because Go 1.25 adds a feature to dynamically set GOMAXPROC based on current CPU quota values. This feature can be disabled by setting GODEBUG=containermaxprocs=0,updatemaxprocs=0 but it is harmless to keep it (except for the above test failure). Add an exception to the test case. 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.