Change Details

Follows https://docs.pytest.org/en/stable/fixture.html#dynamic-scope to enable dynamic scope for docker fixtures. The odd thing is that session scope is still not supported since `request.fspath` is not available then. In the future, if we want to enable this, we should refactor request.fspath out. This could probably be done by just getting rid of the high level fixture of `docker_compose` in favor `docker_compose_cm`, but don't feel strongly about this. The ability for `docker_compose` to automatically find the docker compose file to setup is nice quality of life, but if we look more deeper into having some shared test infrastructure, it might be nice to enable session scoped fixtures to prevent infra from being setup multiple times during a test suite.

The setup and teardown for these docker compose fixtures are beefy. They should only be initialized once per module (test file). It should be the responsibility of the one writing tests to ensure proper cleanup in between tests (e.g. database wiped, queue cleared, etc).

Follows https://docs.pytest.org/en/stable/fixture.html#dynamic-scope to enable dynamic scope for docker fixtures. The odd thing is that session scope is still not supported since `request.fspath` is not available then. In the future, if we want to enable this,The setup and teardown for these docker compose fixtures are beefy. weThey should refactor request.fspathonly be initialized once per module (test file). out. This could probably be done by just getting rid of the high level fixture of `docker_compose` in favor `docker_compose_cm`, but don't feel strongly about thisIt should be the responsibility of the one writing tests to ensure proper cleanup in between tests (e.g. The ability for `docker_compose` to automatically find the docker compose file to setup is nice quality of lifedatabase wiped, but if we look more deeper into having some shqueue cleared test infrastructure, it might be nice to enable session scoped fixtures to prevent infra from being setup multiple times during a test suiteetc).