Hi Dagster team,
Is there a built in way in the testing framework for dagster to mock successful runs / outputs of runs instead of triggering the run as the test? Correct me if I'm wrong, but it seems like a lot of the examples for tests use a framework where they execute a run and use the results of it / output of it as part of the testing. The issue we have is that in some cases, we don't care about the real output of the run. We want to evaluate what happens when various outputs are produced from the run itself (i.e. if they successfully trigger sensors, etc.)?
03/03/2023, 3:59 AM
Is this for a unit test where you’re invoking a sensor?