Makefile is used to automate Pyroute2 deployment and test processes. Mostly, it is but a collection of common commands.
Clean up the repo directory from the built documentation, collected coverage data, compiled bytecode etc.
Build documentation. Requires sphinx.
Build API documentation. Requires epydoc.
Pls notice that epydoc is discontinued. The reason to support it here is that it performs additional API testing and helps to highlight API inconsistencies.
No issues regarding epydoc output format are accepted.
Run tests against current code. Command line options:
To run the full test cycle on the project, using a specific python, making html coverage report:
$ sudo make test python=python3 coverage=html
To run a specific test module:
$ sudo make test module=general:test_ipdb.py:TestExplicit
The module parameter syntax:
## module=package[:test_file.py[:TestClass[.test_case]]]
$ sudo make test module=lnst
$ sudo make test module=general:test_ipr.py
$ sudo make test module=general:test_ipdb.py:TestExplicit
There are several test packages:
For each package a new Python instance is launched, keep that in mind since it affects the code coverage collection.
It is possible to skip tests by a pattern:
$ sudo make test skip=test_stress
Run tests on isolated VMs defined by tests/ci/configs/*xml.
Requires qemu, kvm, libvirt and civm script: https://github.com/svinota/civm
Command line options:
Build and install the package into the system. Command line options:
Build the package and deploy the egg-link with setuptools. No code will be deployed into the system directories, but instead the local package directory will be visible to the python. In that case one can change the code locally and immediately test it system-wide without running make install.
Other targets are either utility targets to be used internally, or hooks for related projects. You can safely ignore them.