Testing with GitHub Actions

Autoreduction uses GitHub Actions for continuous integration. You can find the GitHub Actions output here. Autoreduction uses GitHub Actions for:

• pylint - A linting tool designed to find static problems with code
• pytest - Run unit/system tests and generate coverage information (linked to coveralls)
• selenium - Automated webapp browser testing
• validate build process - whilst this isn't an explicit test in GitHub Actions, we have to build/install autoreduction in order to test it
• code scanning - Performs static analysis on the code base for security vulnerabilities and code improvements. Runs at 05:00 every Monday or can be run manually here using the workflow_dispatch event

The GitHub Actions configuration (running instructions) can be found in .github/workflows/ and .github/actions/. If you wish to make changes to the build configuration of GitHub Actions try to do this in a separate issue/pull request where it makes sense to do so.