pico-testing 0.1.0

Pytest plugin for the Pico ecosystem: isolated containers by default and a make_container fixture.

pico-testing

Pytest plugin for the pico ecosystem: isolated containers by default and a make_container fixture with automatic shutdown.

Why

Any pico_boot.init() in a test auto-discovers every pico plugin installed in the venv — so a test suite passes or fails depending on what else happens to be installed. Every pico project ends up copying the same two conftest fixtures. This plugin ships them once:

• Isolation by default: PICO_BOOT_AUTO_PLUGINS=false is set for every test. Opt back in per-test with @pytest.mark.pico_auto_plugins.
• make_container: builds containers from explicit modules and config, and shuts them all down on teardown.

Installation

pip install pico-testing

No conftest wiring — installing it activates the plugin.

Quick start

import sys

def test_my_service(make_container):
    container = make_container(
        "my_package",
        config={"my_prefix": {"key": "value"}},
    )
    service = container.get(MyService)
    assert service.do_something() == "expected"

make_container(*modules, config=None, boot=False):

• modules: module objects or import strings, passed to init(modules=[...]).
• config: a plain dict (wrapped in configuration(DictSource(...))) or a ready configuration(...) object.
• boot=True: use pico_boot.init instead of pico_ioc.init (plugin auto-discovery still off unless the test is marked).

Re-enable plugin auto-discovery for a single test:

import pytest

@pytest.mark.pico_auto_plugins
def test_full_boot(make_container):
    container = make_container(boot=True)

Documentation

Full documentation: https://dperezcabrera.github.io/pico-testing/

License

MIT