Page MenuHomeElementl

test: default docker compose fixtures to be module scoped
Needs ReviewPublic

Authored by rexledesma on Jul 23 2021, 8:14 PM.
Referenced Files
Unknown Object (File)
Fri, Nov 18, 1:38 AM
Unknown Object (File)
Fri, Nov 18, 1:38 AM
Unknown Object (File)
Fri, Nov 18, 1:38 AM
Unknown Object (File)
Mon, Nov 14, 8:49 PM
Unknown Object (File)
Fri, Nov 4, 5:06 AM
Unknown Object (File)
Thu, Nov 3, 4:14 AM
Unknown Object (File)
Oct 29 2022, 8:01 PM
Unknown Object (File)
Oct 28 2022, 4:58 AM
This revision needs review, but all specified reviewers are disabled or inactive.



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).

Test Plan

Diff Detail

R1 dagster
rl/docker-stuff (branched from master)
Lint Passed
No Test Coverage

Event Timeline

I'd like to see it in action - I don't have a great sense of how this actually gets used and adding a test to describe that behavior would be great.

Alternatively, what if we made the these all module scoped by default - and if you want a function scoped one, you can nest the call in a function scoped fixture (since more narrowly scoped fixtures can request more broadly scoped ones - but not the inverse). There's not a particular reason I made these function scoped - just that it's the default behavior.


Can you include a test that shows how this is used?

This revision now requires changes to proceed.Jul 23 2021, 9:12 PM
rexledesma retitled this revision from test: allow docker compose fixture to be session scoped to test: default docker compose fixtures to be module scoped.Jul 27 2021, 2:35 PM
rexledesma edited the summary of this revision. (Show Details)