Feature: pytest integration

[alexanderankin]

todo fill this out
todo decide if this is a good idea

What are you trying to do?

Describe the intention of the enhancement.

Why should it be done this way?

Describe the motivation of the enhancement.

Other references:

Include any other relevant reading material about the enhancement.

[jackburridge]

This could be useful for reducing boilerplate, especially for common cases where users want a container fixture to be available without having to define it themselves.

My main question is how fixture scope would be handled.

In practice, I often need explicit control over scope depending on the test suite. For example, in one of my projects I keep the Kafka container alive across multiple tests to improve test speed:

@pytest.fixture(scope="module")
def kafka_container() -> Generator[KafkaContainer, None, None]:
    with KafkaContainer(image="ghcr.io/asyncfast/cp-kafka:7.6.0") as kafka_container:
        yield kafka_container

If a pytest plugin automatically provides fixtures for containers, how would cases like this be handled?

Would users be expected to override the plugin fixture locally if they want a different scope?

Another consideration is image configuration. In my case I often override the default image to avoid Docker Hub pull limits and instead pull from GHCR:

with KafkaContainer(image="ghcr.io/asyncfast/cp-kafka:7.6.0")

If the plugin provides default fixtures, how would this kind of customization be handled? For example, would there be a way to configure the image globally (e.g. via pytest config or environment variables).

[rhoban13]

If the plugin provides default fixtures, how would this kind of customization be handled?

This is my main question. I tried to do similar with some containers internal to my work, and immediately ran into the fact that there's no real clean way to pass data from a test "up" to a fixture (I find indirect fixture parametrization kinda confusing).