test: add test with multiple ORM schemas

[vincentchalamon]

Fixes #618

[kbond]

This looks great, thanks for working on this Vincent!

Regarding the failing CI (I'm not familiar with multiple schemas). Do you know what's going on there?

[kbond]

Can we use Symfony\Component\Filesystem\Filesystem to just copy the entire directory?

[vincentchalamon]

Filesystem only allows to copy files, not directories

[kbond]

Filesystem::mirror() should do the trick (but this isn't a big deal)

[vincentchalamon]

Hi @kbond,

Regarding the failing CI (I'm not familiar with multiple schemas). Do you know what's going on there?

The doctrine:schema:update command doesn't seem to support multiple schemas. To handle such specific use case, I had to separate migrate mode from schema mode fixtures. Push in progress.

This PR is still in WIP till I find a clean solution to test this specific use case.

[nikophil]

Hi @vincentchalamon

I'm wondering if a simpler solution would not be to declare two entity managers, affect one entity to this entity manager, and configure the test kernel to not reset this specific EM. WDYT?

[vincentchalamon]

Hi @vincentchalamon

I'm wondering if a simpler solution would not be to declare two entity managers, affect one entity to this entity manager, and configure the test kernel to not reset this specific EM. WDYT?

I'm afraid using multiple entity managers won't solve the original issue. The idea is to add non-regression tests to ensure the database is fully and properly removed before running the migrations (cf. #615).

The idea here is to have a custom migration which should fail the tests if not run properly (for instance, if AbstractORMPersistenceStrategy::resetSchema method is updated).

[nikophil]

ok thanks for explanations, I understand better now!