jupyterhub / pytest-jupyterhub

Reusable pytest plugin for testing JupyterHub's components
https://pytest-jupyterhub.readthedocs.io/en/latest/
BSD 3-Clause "New" or "Revised" License
5 stars 5 forks source link

Description | Installation | Usage | Contributing


Reusable JupyterHub Pytest Plugin

Latest PyPI version Documentation status GitHub Workflow Status - Test GitHub Test coverage of code

Description

This is a reusable pytest plugin for testing JupyterHub's components

JupyterHub is a modular and extensible project, with components, like the proxy, authenticator and spawner, that can be easily replaced with alternate implementations. Testing the functionality of these components against JupyterHub is important and it requires various hub setups that can sometimes become complicated.

Each of these hub components and the hub itself define their own testing infrastructure, building everything from the ground up using the pytest framework. And some of this complex work is either repetitive across JupyterHub sub-projects, or under-specified for some of them. This has sparked a need to abstract these common parts into a separate testing framework.

The goal is to provide importable testing utilities to make it easier for contributors to write tests for the various hub components. This will involve creating and using fixtures and mocks.

A Fixture is a function that is used to prepare and clean up the environment for a test function. Fixtures can be used to set up test data, test environment, and other resources that are needed by test functions. For more information on Fixtures, check out this pytest documentation on fixtures.

A Mock is an object that simulates the behavior of another object such as a class or function. They are used to simulate the behavior of real objects for testing purposes. For more information on Mocks, check out this unittest documentation on the mock module.

Installation

To use the JupyterHub Pytest Plugin, you will first need to install it using pip:

pip install pytest-jupyterhub

Usage

To use a plugin, first register/load the plugin in your test module or conftest.py file:

pytest_plugins = "jupyterhub-spawners-plugin"

To register multiple plugins:

pytest_plugins = ["jupyterhub-spawners-plugin", "other-plugin"]

For more information, check out this document on Requiring/Loading plugins in a test module or conftest file

All fixtures and mocks inside the plugin will be available to all of your project's test suites. You can use a fixture by passing it as an argument to your test function.

Example

The hub_app fixture is a factory fixture that creates a MockHub instance from a provided config dictionary defining spawner-specific attribute configurations. It then yields the mocked instance. After testing, the running hub instance is stopped and a cleanup is performed.

An illustration of its integration within the DockerSpawner test suite is provided below:

@pytest.fixture
async def app(hub_app):
    config = {
        "Dockerspawner": {
            "prefix": "dockerspawner-test"
        }
    }

    if len(jh_version_info) > 3 and jh_version_info[3]:
        tag = jupyterhub.__version__
        config["Dockerspawner"]["image"] = f"jupyterhub/singleuser:{tag}"

    app = await hub_app(config=config)

    return app

Contributing

If you would like to contribute to the project, please read our contributor documentation and the CONTRIBUTING.md.

The contributor documentation explains how to set up a development installation, how to run the test suite, and how to contribute to documentation.