Page MenuHomeElementl

Introduce docker compose fixtures

Authored by jordansanders on Jul 2 2021, 8:10 PM.
Referenced Files
Unknown Object (File)
Mon, May 29, 3:02 PM
Unknown Object (File)
Thu, May 25, 9:15 PM
Unknown Object (File)
Thu, May 25, 9:32 AM
Unknown Object (File)
Sat, May 13, 4:02 PM
Unknown Object (File)
May 1 2023, 2:49 AM
Unknown Object (File)
Apr 10 2023, 2:10 AM
Unknown Object (File)
Apr 2 2023, 8:02 AM
Unknown Object (File)
Mar 26 2023, 9:50 PM



These pytest fixtures aim to replace much of what we currently do in

The two biggest benefits of this approach are:

  1. Conditional environment logic (i.e. different behavior when running on Buildkite) is relegated to the fixtures instead of living in the tests. While we'll still have two paths through every test that uses docker compose (one that uses localhost and one that jumps through some separate networking hoops), that branching will only live in a single place instead of repeating it over and over in each test.
  2. We can build more interesting test scenarios in pure Python. For example, with the old approach, if you wanted to do any setup before docker compose up, you needed to offload that test setup into a script and call it from the Buildkite step. Now, you can handle that test setup in pure Python inside your test fixtures.

There are two types of fixtures being introduced here:

  1. A higher level docker_compose fixture that's not customizable, but operates like a true Pytest fixture. You can use this if your docker-compose.yml lives in your test directory and if there's no additional setup or customization you need by simply including the fixture name as an argument to your test.
  2. A lower level docker_compose_cm fixture that yields a customizable contextmanager. This can be chained with other fixtures to produce highly customizable test setup.

These fixtures can be imported individually. Alternatively, as long as
dagster_test is installed, you can have test suites automatically
discover them via any of Pytest's plugin discovery options:

Initially, I'm setting the pytest_plugins variable in test suites that
use this. Eventually, I'd like to configure Buildkite and our
pyproject.toml to automatically include them in all of our tests - but
doing that requires some more intentional thought around _where_ these
fixtures should live. I see a few different options:

  • dagster_test - where I've chosen to place them initially. But I'm not sure we'd ever want this to be a dependency of _all_ libraries.
  • dagster - similar to where we put But it seems odd to include pytest as a dependency of dagster.
  • A new library - perhaps dagster-pytest - that gets published to pypi. Although this is all specific to _our_ testing setup on Buildkite. A package with that name might be better as a customer-facing package with fixtures that allow you to easily test your own dagster code.
Test Plan


Diff Detail

R1 dagster
Lint Not Applicable
Tests Not Applicable

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Jul 2 2021, 8:32 PM
Harbormaster failed remote builds in B33121: Diff 40822!

Always use absolute path so that we correctly infer the basename from the current working directory's docker-comopse.yml file

Harbormaster returned this revision to the author for changes because remote builds failed.Jul 2 2021, 9:04 PM
Harbormaster failed remote builds in B33138: Diff 40843!

Awesome! Could move description from the diff to code comments


So to use this, I'd call the docker_compose_cm with a fixed network name inside a fixture named network?


oh nice, this is a default temp dir?

This revision is now accepted and ready to land.Jul 6 2021, 2:46 PM

Yup! Or not even strictly _inside_ a fixture named network - just from somewhere that your network has already been created (or will be created by the time docker-compose up finishes running.

So that could be inside a test that already relies on a network fixture. Or that could be from within a network fixture. Or that could be relying on the name of a network that's defined in the docker-compose.yml that you plan on using.


It's actually the directory where the test was collected from.

So if you have:


and you run pytest, then your cwd will obviously be wherever pytest is invoked from. request.fspath will be the path to the file where the test comes from. And test_directory will be the path to the directory where that file lives.

So for any test in, test_directory will return test_foo/test_bar which makes it easier for us to then identify test_foo/test_bar/docker-compose.yml

This revision was automatically updated to reflect the committed changes.