The GitHub CI/CD (or "Actions") can be used to implement testing frameworks directly on Github. One can define certain jobs that are excecuted on push, pull-request, or other events. It is commonly used for:
Static code checking: Linter (flake8), formatter (e.g. black), dead code finder (e.g. vulture), ...
Testing: Integration and unit tests (using pytest)
Documentation: Build and deploy html code documentation (e.g. sphinx, doygen)
Building the code on different platforms (using platform specifiers for jobs or docker container)
Building and deploying docker container (Github container registry)
The easiest one to implement is a testing framework using pytest. In contrast to the currently used tool travis, a testing framework using pytest and Github actions is free and directly integrated into the Github GUI (see "Actions" tab). Morover, a coverage report in html format is generated and published as an artifact to be downloaded if desired (shows which LOCs are covered in tests and which are not)
richterjakob
commented
2 years ago
The GitHub CI/CD (or "Actions") can be used to implement testing frameworks directly on Github. One can define certain jobs that are excecuted on push, pull-request, or other events. It is commonly used for:
flake8), formatter (e.g.black), dead code finder (e.g.vulture), ...pytest)sphinx,doygen)The easiest one to implement is a testing framework using pytest. In contrast to the currently used tool travis, a testing framework using pytest and Github actions is free and directly integrated into the Github GUI (see "Actions" tab). Morover, a coverage report in html format is generated and published as an artifact to be downloaded if desired (shows which LOCs are covered in tests and which are not)
Interested parties
@mrp089