UPG End-to-End (E2E) tests run VPP with UPG plugin as a subprocess in a separate network namespace, making it pass traffic between other network namespaces while trying to break it in different ways.
The tests are written in Go to provide acceptable performance for timing-sensitive tests while still being easy enough to maintain.
The following packages need to be present in the system (Ubuntu/Debian) to run E2E tests, unless dockerized environment is used:
- gdb
- golang-go (preferably 1.15, e.g. from golang-backports)
- libpcap-dev
The tests are invoked from the top project directory using either
make e2e-debug
or make e2e-release
commands.
The make commands accept following variables:
E2E_RETEST
: if non-empty, don't build UPG before starting the testsE2E_VERBOSE
: if non-empty, enable verbose output for the testsE2E_PARALLEL
: if non-empty, run tests in parallelE2E_PARALLEL_NODES
: specify the number of parallel processes (nodes) for parallel testingE2E_FOCUS
: an optional regexp for selecting a subset of tests to run by nameE2E_SKIP
: an optional regexp for selecting a subset of tests to skip by nameE2E_ARTIFACTS_DIR
: target directory for test artifacts (note, must start with /src in case of Docker env, where/src
corresponds to the project root)E2E_JUNIT_DIR
: target directory for test reports in JUnit XML formatE2E_QUICK
: do shorter tests (pass less traffic)E2E_FLAKE_ATTEMPTS
: retry failed tests specified amount of timesE2E_TRACE
: enable VPP traceE2E_DISPATCH_TRACE
: store the VPP dispatch trace asdispatch-trace.pcap
in the test dirE2E_PAUSE_ON_ERROR
: pause on error for interactive debuggingE2E_MULTICORE
: run tests with a single worker core enabledE2E_KEEP_ALL_ARTIFACTS
: store artifacts even for successful tests
An example with multiple flags:
make e2e-debug \
E2E_QUICK=1 \
E2E_ARTIFACTS_DIR=/src/artifacts \
E2E_JUNIT_DIR=/src/junit \
E2E_PARALLEL=y \
E2E_PARALLEL_NODES=4 \
E2E_FOCUS=PGW