CI strategy

We use continuous integration to continuously run a range of tests and checks on our code.

Overview

The standard .github/workflows/gh-ci.yaml workflow configuration file for GitHub-actions and azure-pipelines.yml for Azure contains

1. functional/unit tests (pytest)
2. coverage (of the unit tests)
3. doctests
4. performance benchmarks (asv)
5. sdist package build

External variables: Test matrix

Elements of the test matrix are the operating system, architecture, and the source of the dependency installation. We do not test a full Cartesian product of all possibilities. Instead different runners cover subsets.

(TODO: describe which runner does what and why)

Operating systems

• Linux
• macOS
• Windows

Architectures

• x86_64
• arm64 (macOS) – GH runners
• arm64 (Linux) — CircleCI (?)

numpy version

• minimal
• latest

Installation source of dependencies

• PyPi (pip installation)
• conda-forge (mamba installation)