Testing with Dagster dg

.devcontainer/dagster-testing/Dockerfile

@@ -1,7 +1,7 @@
 FROM mcr.microsoft.com/devcontainers/python:0-3.11-bullseye
 ENV PYTHONUNBUFFERED 1
 
-COPY --from=ghcr.io/astral-sh/uv:0.4.7 /uv /bin/uv
+COPY --from=ghcr.io/astral-sh/uv:0.6.10 /uv /bin/uv
 
 COPY dagster_university/dagster_testing/pyproject.toml .
 RUN uv pip install -r pyproject.toml --system

course/pages/dagster-testing/lesson-2/1-set-up-local.md

@@ -6,6 +6,8 @@ lesson: '2'
 
 # Set up local
 
+This will set up Dagster for you local machine. If you would prefer to do this course in Github Codespaces, please follow [that guide](/dagster-testing/lesson-2/2-set-up-codespace).
+
 - **To install git.** Refer to the [Git documentation](https://github.com/git-guides/install-git) if you don’t have this installed.
 - **To have Python installed.**  Dagster supports Python 3.9 - 3.12.
 - **To install a package manager**. To manage the python packages, we recommend [`uv`]((https://docs.astral.sh/uv/)) which Dagster uses internally.
@@ -34,38 +36,37 @@ After cloning the Dagster University project, you’ll want to navigate to speci
 cd dagster_university/dagster_testing
 ```
 
-## Install the dependencies
+## Install uv and dg
 
-**uv**
+Now we want to install `dg`. This is the command line interface that makes it easy to interact with Dagster. Throughout the course we will use `dg` to scaffold our project and streamline the development process.
 
-To install the python dependencies with [uv](https://docs.astral.sh/uv/).
+In order to best use `dg` we will need the Python package manager [`uv`](https://docs.astral.sh/uv/). `uv` will allow us to install `dg` globally and more easily build our virtual environments.
 
+If you do not have `uv` instead already, you can do so with:
 ```bash
-uv sync
+brew install uv
 ```
 
-This will create a virtual environment that you can now use.
-
+Now you can use `uv` to install `dg` globally:
 ```bash
-source .venv/bin/activate
+uv tool install dagster-dg
 ```
 
-**pip**
-
-Create the virtual environment.
+## Install the dependencies
 
+With `uv` and `dg` set, we can create the virtual environment specific to this course. All of the dependencies are maintained in the `pyproject.toml` (you will not need to edit anything in that project for this course). To create the virtual environment, run:
 ```bash
-python3 -m venv .venv
+uv sync
 ```
 
-Enter the virtual environment.
+This will create a virtual environment and install all the necessary dependencies. To activate this virtual environment:
 
 ```bash
 source .venv/bin/activate
 ```
 
-Install the packages.
+To ensure everything is working you can launch the Dagster UI.
 
 ```bash
-pip install -e ".[dev]"
+dg dev
 ```

course/pages/dagster-testing/lesson-2/2-set-up-codespace.md

@@ -41,7 +41,7 @@ cd dagster_university/dagster_testing
 To ensure everything is working you can launch the Dagster UI.
 
 ```bash
-dagster dev
+dg dev
 ```
 
 After Dagster starts running you will be prompted to open the Dagster UI within your browser. Click "Open in Browser".

course/pages/dagster-testing/lesson-3/1-unit-tests.md

@@ -34,7 +34,7 @@ Dagster assets are good candidates for unit tests. Since an asset is responsible
 We will begin with the following asset:
 
 ```python
-# /dagster_testing/assets/lesson_3.py
+# /dagster_testing/defs/assets/lesson_3.py
 @dg.asset
 def state_population_file() -> list[dict]:
     file_path = Path(__file__).absolute().parent / "../data/ny.csv"

course/pages/dagster-testing/lesson-3/2-testing-dependencies.md

@@ -11,7 +11,7 @@ Most Dagster asset graphs contain multiple assets that depend on the output of o
 We will add an additional asset downstream of `state_population_file` that takes in its output:
 
 ```python
-# /dagster_testing/assets/lesson_3.py
+# /dagster_testing/defs/assets/lesson_3.py
 @dg.asset
 def total_population(state_population_file: list[dict]) -> int:
     return sum([int(x["Population"]) for x in state_population_file])

course/pages/dagster-testing/lesson-3/3-testing-assets-with-run-configurations.md

@@ -11,7 +11,7 @@ Some assets in Dagster pipelines may take in parameters defined outside of asset
 If we think about the `state_population_file` it can currently only parse a single file. Let's create a new asset called `state_population_file_config` with a run configuration. This asset will be able to process any file:
 
 ```python
-# /dagster_testing/assets/lesson_3.py
+# /dagster_testing/defs/assets/lesson_3.py
 class FilepathConfig(dg.Config):
     path: str
 

course/pages/dagster-testing/lesson-3/4-testing-asset-output-types.md

@@ -9,7 +9,7 @@ lesson: '3'
 In standard Python, a function does not need to match its type annotation in order to execute properly. For example:
 
 ```python
-# /dagster_testing/assets/lesson_3.py
+# /dagster_testing/defs/assets/lesson_3.py
 def func_wrong_type() -> str:
     return 2
 ```

course/pages/dagster-testing/lesson-3/5-testing-assets-with-execution-context.md

@@ -13,7 +13,7 @@ If your assets do not access any of the context APIs, you will not need to worry
 However if we rewrite the `state_population_file` asset to include context logging, we will need to update our tests:
 
 ```python
-# /dagster_testing/assets/lesson_3.py
+# /dagster_testing/defs/assets/lesson_3.py
 @dg.asset()
 def state_population_file_logging(context: dg.AssetExecutionContext) -> list[dict]:
     file_path = Path(__file__).absolute().parent / "../data/ny.csv"

course/pages/dagster-testing/lesson-4/1-testing-with-mocks.md

@@ -30,7 +30,7 @@ Imagine that an API exists to query city populations by state (sadly this API do
 We want to rewrite the `state_population_file` asset to use this endpoint instead of reading a file to retrieve the necessary data. This is what the new asset will look like.
 
 ```python
-# /dagster_testing/assets/lesson_4.py
+# /dagster_testing/defs/assets/lesson_4.py
 API_URL = "https://fake.com/population.json"
 
 

course/pages/dagster-testing/lesson-4/2-testing-with-resources.md

@@ -13,7 +13,7 @@ Resources are objects that provide access to external systems, databases, or ser
 We can refactor the API asset code into a resource. A resource is just a class that inherits from `dg.ConfigurableResource`. It can have any number of methods which assets can use. This resource will only include a single method for `get_cities`.
 
 ```python
-# /dagster_testing/assets/lesson_4.py
+# /dagster_testing/defs/assets/lesson_4.py
 class StatePopulation(dg.ConfigurableResource):
     def get_cities(self, state: str) -> list[dict]:
         output = []

course/pages/dagster-testing/lesson-4/3-materializing-resource-tests.md

@@ -9,7 +9,7 @@ lesson: '4'
 When we discussed unit tests we showed how you can execute one or more assets together using `dg.materialize()`. We can still materialize our assets this way using mocks.
 
 ```python
-# /dagster_testing/assets/lesson_4.py
+# /dagster_testing/defs/assets/lesson_4.py
 @patch("requests.get")
 def test_state_population_api_assets(mock_get, example_response, api_output):
     mock_response = Mock()

course/pages/dagster-testing/lesson-5/2-integration-tests.md

@@ -19,7 +19,7 @@ Assume a table exists in our production data warehouse, `data.city_population`,
 We will hardcode our asset to look for the cities in New York and return the results from Snowflake using a resource.
 
 ```python
-# /dagster_testing/assets/lesson_5.py
+# /dagster_testing/defs/assets/lesson_5.py
 @dg.asset
 def state_population_database(database: SnowflakeResource) -> list[tuple]:
     query = """

course/pages/dagster-testing/lesson-6/1-asset-checks.md

@@ -23,7 +23,7 @@ When the asset runs, we can see that its associated asset checks also run and va
 To define an asset check we first need an asset. `total_population` is a slightly modified version of the asset we have used throughout the course. Now it will take in the output of several assets and sums their populations.
 
 ```python
-# /dagster_testing/assets/lesson_6.py
+# /dagster_testing/defs/assets/lesson_6.py
 @dg.asset
 def total_population(
     state_population_file_config: list[dict],

course/pages/dagster-testing/lesson-6/2-definitions.md

@@ -6,7 +6,9 @@ lesson: '6'
 
 # Definitions
 
-Within your Dagster project the most important object is the definition. This defines all the objects that will deployed into your code location. Because of its importance we will want to write a test for it.
+Within your Dagster project the most important object is the `Definitions`. This defines all the objects that will deployed into your code location. If you are using `dg` you may already be in the habit of checking to ensure your `Definitions` is valid by running `dg check defs`.
+
+This is a great habit and you can build out workflows (such as precommit hooks) to always run that check. But it is also good to get in the habit of writing a specific test for this to live alongside your other Dagster tests.
 
 Luckily this is a very easy test to write.
 

course/pages/dagster-testing/lesson-6/3-dagster-objects.md

@@ -128,7 +128,7 @@ In order to write a reliable test for this sensor, we will go back to our lesson
 First we can set a test where our sensor will skip.
 
 ```python
-@patch("dagster_testing.sensors.check_for_new_files", return_value=[])
+@patch("dagster_testing.defs.sensors.check_for_new_files", return_value=[])
 def test_sensor_skip(mock_check_new_files):
     instance = dg.DagsterInstance.ephemeral()
     context = dg.build_sensor_context(instance=instance)
@@ -152,7 +152,7 @@ What would it look like to write a test to ensure the sensor picks up a new file
 
 ```python {% obfuscated="true" %}
 @patch(
-    "dagster_testing.sensors.check_for_new_files",
+    "dagster_testing.defs.sensors.check_for_new_files",
     return_value=["test_file"],
 )
 def test_sensor_run(mock_check_new_files):

dagster_university/dagster_testing/dagster_testing/definitions.py

@@ -1,25 +1,5 @@
 import dagster as dg
 
-import dagster_testing.jobs as jobs
-import dagster_testing.resources as resources
-import dagster_testing.schedules as schedules
-import dagster_testing.sensors as sensors
-from dagster_testing.assets import lesson_3, lesson_4, lesson_5, lesson_6
+import dagster_testing.defs
 
-lesson_3_assets = dg.load_assets_from_modules([lesson_3])
-lesson_4_assets = dg.load_assets_from_modules([lesson_4])
-lesson_5_assets = dg.load_assets_from_modules([lesson_5])
-lesson_6_assets = dg.load_assets_from_modules([lesson_6])
-
-
-defs = dg.Definitions(
-    assets=lesson_3_assets + lesson_4_assets + lesson_5_assets + lesson_6_assets,
-    asset_checks=[lesson_6.non_negative],
-    jobs=[jobs.my_job, jobs.my_job_configured],
-    resources={
-        "state_population_resource": resources.StatePopulation(),
-        "database": dg.ResourceDefinition.mock_resource(),
-    },
-    schedules=[schedules.my_schedule],
-    sensors=[sensors.my_sensor],
-)
+defs = dg.components.load_defs(dagster_testing.defs)

dagster_university/dagster_testing/dagster_testing/assets/lesson_6.py → dagster_university/dagster_testing/dagster_testing/defs/assets/lesson_6.py

@@ -3,7 +3,7 @@
 
 import dagster as dg
 
-import dagster_testing.resources as resources
+import dagster_testing.defs.resources as resources
 
 
 class FilepathConfig(dg.Config):

dagster_university/dagster_testing/dagster_testing/jobs.py → dagster_university/dagster_testing/dagster_testing/defs/jobs.py

@@ -3,7 +3,7 @@
 import dagster as dg
 import yaml
 
-from dagster_testing.assets import lesson_6
+from dagster_testing.defs.assets import lesson_6
 
 my_job = dg.define_asset_job(
     name="jobs",

dagster_university/dagster_testing/dagster_testing/resources.py → dagster_university/dagster_testing/dagster_testing/defs/resources.py

@@ -13,3 +13,11 @@ def get_cities(self, state: str) -> list[dict]:
                 "Population": 269840,
             },
         ]
+
+
+defs = dg.Definitions(
+    resources={
+        "state_population_resource": StatePopulation(),
+        "database": dg.ResourceDefinition.mock_resource(),
+    },
+)

dagster_university/dagster_testing/dagster_testing/schedules.py → dagster_university/dagster_testing/dagster_testing/defs/schedules.py

@@ -1,7 +1,7 @@
 import dagster as dg
 
-import dagster_testing.jobs as jobs
-from dagster_testing.assets import lesson_6
+import dagster_testing.defs.jobs as jobs
+from dagster_testing.defs.assets import lesson_6
 
 my_schedule = dg.ScheduleDefinition(
     name="my_schedule",

dagster_university/dagster_testing/dagster_testing/sensors.py → dagster_university/dagster_testing/dagster_testing/defs/sensors.py

@@ -2,7 +2,7 @@
 
 import dagster as dg
 
-import dagster_testing.jobs as jobs
+import dagster_testing.defs.jobs as jobs
 
 
 def check_for_new_files() -> list[str]:

dagster_university/dagster_testing/dagster_testing_tests/completed/test_lesson_3.py

@@ -5,7 +5,7 @@
 import yaml
 from dagster._core.errors import DagsterTypeCheckDidNotPass
 
-from dagster_testing.assets import lesson_3
+from dagster_testing.defs.assets import lesson_3
 
 
 @pytest.fixture()

dagster_university/dagster_testing/dagster_testing_tests/completed/test_lesson_4.py

@@ -3,7 +3,7 @@
 import dagster as dg
 import pytest
 
-from dagster_testing.assets import lesson_4
+from dagster_testing.defs.assets import lesson_4
 
 
 @pytest.fixture

dagster_university/dagster_testing/dagster_testing_tests/completed/test_lesson_5.py

@@ -5,7 +5,7 @@
 import pytest
 from dagster_snowflake import SnowflakeResource
 
-from dagster_testing.assets import lesson_5
+from dagster_testing.defs.assets import lesson_5
 
 from ..fixtures import docker_compose  # noqa: F401
 

dagster_university/dagster_testing/dagster_testing_tests/completed/test_lesson_6.py

@@ -4,12 +4,12 @@
 import dagster as dg
 import pytest
 
-import dagster_testing.jobs as jobs
-import dagster_testing.resources as resources
-import dagster_testing.schedules as schedules
-import dagster_testing.sensors as sensors
-from dagster_testing.assets import lesson_6
+import dagster_testing.defs.jobs as jobs
+import dagster_testing.defs.resources as resources
+import dagster_testing.defs.schedules as schedules
+import dagster_testing.defs.sensors as sensors
 from dagster_testing.definitions import defs
+from dagster_testing.defs.assets import lesson_6
 
 
 @pytest.fixture()
@@ -128,15 +128,15 @@ def test_sensors():
     assert sensors.my_sensor
 
 
-@patch("dagster_testing.sensors.check_for_new_files", return_value=[])
+@patch("dagster_testing.defs.sensors.check_for_new_files", return_value=[])
 def test_sensor_skip(mock_check_new_files):
     instance = dg.DagsterInstance.ephemeral()
     context = dg.build_sensor_context(instance=instance)
     assert sensors.my_sensor(context).__next__() == dg.SkipReason("No new files found")
 
 
 @patch(
-    "dagster_testing.sensors.check_for_new_files",
+    "dagster_testing.defs.sensors.check_for_new_files",
     return_value=["test_file"],
 )
 def test_sensor_run(mock_check_new_files):

dagster_university/dagster_testing/dagster_testing_tests/test_lesson_3.py

@@ -4,7 +4,7 @@
 import yaml  # noqa: F401
 from dagster._core.errors import DagsterTypeCheckDidNotPass  # noqa: F401
 
-from dagster_testing.assets import lesson_3
+from dagster_testing.defs.assets import lesson_3
 
 
 @pytest.fixture()

dagster_university/dagster_testing/dagster_testing_tests/test_lesson_4.py

@@ -3,7 +3,7 @@
 import dagster as dg  # noqa: F401
 import pytest
 
-from dagster_testing.assets import lesson_4  # noqa: F401
+from dagster_testing.defs.assets import lesson_4  # noqa: F401
 
 
 @pytest.fixture

dagster_university/dagster_testing/dagster_testing_tests/test_lesson_5.py

@@ -5,7 +5,7 @@
 import pytest
 from dagster_snowflake import SnowflakeResource
 
-from dagster_testing.assets import lesson_5
+from dagster_testing.defs.assets import lesson_5
 
 from .fixtures import docker_compose  # noqa: F401
 

dagster_university/dagster_testing/dagster_testing_tests/test_lesson_6.py

@@ -1,10 +1,10 @@
 import pytest
 
-import dagster_testing.jobs as jobs  # noqa: F401
-import dagster_testing.schedules as schedules  # noqa: F401
-import dagster_testing.sensors as sensors  # noqa: F401
-from dagster_testing.assets import lesson_6  # noqa: F401
+import dagster_testing.defs.jobs as jobs  # noqa: F401
+import dagster_testing.defs.schedules as schedules  # noqa: F401
+import dagster_testing.defs.sensors as sensors  # noqa: F401
 from dagster_testing.definitions import defs
+from dagster_testing.defs.assets import lesson_6  # noqa: F401
 
 
 @pytest.fixture()