Continuous integration#

We use continuous integration services on GitHub to automatically check if new pull requests do not break anything and meet code quality standards such as a common coding style. Before setting up Continuous Integration, be sure that you have set up your developer environment, and installed a developement version

of sktime.

Code quality checks#

We use pre-commit for code quality checks (a process we also refer to as “linting” checks).

We recommend that you also set this up locally as it will ensure that you never run into code quality errors when you make your first PR! These checks run automatically before you make a new commit. To setup, simply navigate to the sktime folder and install our pre-commit configuration:


pre-commit install

pre-commit should now automatically run anything you make a commit! Please let us know if you encounter any issues getting this setup.

For a detailed guide on code quality and linting for developers, see Coding standards.

Unit testing#

We use pytest for unit testing.

To check if your code passes all tests locally, you need to install the development version of sktime and all extra dependencies.

  1. Install the development version of sktime with developer dependencies:

    pip install -e .[dev]

    This installs an editable development version of sktime which will include the changes you make.


For trouble shooting on different operating systems, please see our detailed installation instructions.

  1. To run all unit tests, run:

    make test

or if you don’t have make installed:

pytest ./sktime

Test coverage#

We use coverage, the pytest-cov plugin, and codecov for test coverage.


This section gives an overview of the infrastructure and continuous integration services we use.

Additional scripts used for building, unit testing and distribution can be found in build_tools/.