Don't think fixture would break that. It would just be test code not in the
dag. It would just ensure that the triggerer is running before the tests
that use the triggerer need it. But doing it in breeze makes more sense for
sure. Although I suppose a combination approach could be considered EG,
Thanks for pointing out solutions I hadn't considered.
> we could simply have a pytest fixture that will do the job (based on what
> Daniel proposed).
> It will not support running tests via Airflow UI or regular python execution
> of the test files,
> but maybe it's a good idea that does not
