We should add at least some sort of testing step to validate Pull Requests through github actions. Adding unit tests will probably require quite some refactoring and yield only small result.
I would instead vote for an end-to-end test as a start.
This would include the follwing steps:
This PR will create basic Docker images to run pylint against the current codebase. Once this has been merged, I will open a PR with a GH Action step to this repository so we get at least a very basic check of the code.
We should add at least some sort of testing step to validate Pull Requests through github actions. Adding unit tests will probably require quite some refactoring and yield only small result.
I would instead vote for an end-to-end test as a start. This would include the follwing steps:
This way we learn at least if the code is somewhat working. Any opinions on this?