ee5eb61c41572963299c41489b9acc159cbc246d introduced loading fixtures as tagged services, but also removed the option to specify a path to the fixtures classes.
this created the requirement of having your fixtures within your "main" namespace rather than within your "test" namespace while the loader doesn't really care about that.
would it be an option to re-introduce the --fixtures option so that fixtures can be loaded from a specified path rather than being required to live in the application core?
ee5eb61c41572963299c41489b9acc159cbc246d introduced loading fixtures as tagged services, but also removed the option to specify a path to the fixtures classes.
this created the requirement of having your fixtures within your "main" namespace rather than within your "test" namespace while the loader doesn't really care about that.
would it be an option to re-introduce the
--fixturesoption so that fixtures can be loaded from a specified path rather than being required to live in the application core?