Robert Schmidt
97d0b6534a
There might be various occasions where a CI step should be attempted to be executed, despite a chance of failing. For instance, we might want to try executing an instable Iperf test, and still mark the CI as passing if it fails. This commit introduces a generic "may_fail" option that will mark any CI test as succeeded, despite having failed. Ideally, we would print a warning in the HTML code, but this is not possible because each step emits its own HTML code, instead of the main loop handling this. We can improve this in the future.
In this directory and subdirectories are various CI code test cases and helper scripts.
Unit test
This repository contains unit tests. To run them, switch to the parent
directory, i.e., ci-scripts/, and run
python3 -m unittest tests/*.py
To run individual unit tests, start them like so:
python tests/build.py -v
python tests/cmd.py -v
python tests/corenetwork.py -v
python tests/deployment.py -v
python tests/iperf-analysis.py -v
python tests/ping-iperf.py -v
The logs will indicate if all tests passed. tests/deployment.py requires
these images to be present:
oai-ci/oai-nr-ue:develop-12345678oai-ci/oai-gnb:develop-12345678
It will try to download oaisoftwarealliance/oai-{gnb,nr-ue}:develop
automatically and retag the images.
test-runner test
This is not a true test, because the results need to be manually inspected. To run this "test", run
./run.sh
inside the test-runner/ directory (important!).