DatabaseFixture implementation is hacky and verbose, it implements some host-like behaviour (which is redundant and is a bad practice)
the class needs to be obsoleted, but we still need some "ContainerFixture" class to reduce boilerplate in services.
the analysis of the current service's usage of DatabaseFixture is needed, to figure out what future "PostgresContainerFixture" should look like in a scenario where integration tests makes separate xunit's collection fixture with host and with PostgresContainerFixture as a a child object.
DatabaseFixture implementation is hacky and verbose, it implements some host-like behaviour (which is redundant and is a bad practice)
the class needs to be obsoleted, but we still need some "ContainerFixture" class to reduce boilerplate in services.
the analysis of the current service's usage of DatabaseFixture is needed, to figure out what future "PostgresContainerFixture" should look like in a scenario where integration tests makes separate xunit's collection fixture with host and with PostgresContainerFixture as a a child object.