Behat + Foundry v2 - wrong container again?

[much-rebel]

So a bit while ago I've (and not only me appearantly) had this problem with Foundry v1 booting with app container instead of test on behat setup. Now as I've upgraded project's php and symfony, a v2 Foundry came along and it seems I have same problem again, except the old fix doesn't work anymore as TestState was removed and I have no idea how to pass the test's container now.

A thread about v1 issue: #234

A bit of context follows.

my setup is:

php 8.4
mysql 8.4
symfony 6.4
dama (8.3, not using database reset)
foundry 2.6.0

foundry config:

when@dev: &dev
    zenstruck_foundry:
        auto_refresh_proxies: true

        orm:
            auto_persist: true
            reset:
                connections: [default]
                entity_managers: [default]
                mode: schema

when@test: *dev

if I run this code in the test command (with test env) using cli, all works fine:

protected function execute(InputInterface $input, OutputInterface $output): int
    {
        StaticDriver::setKeepStaticConnections(true);

        $user = UserFactory::new()
            ->password('test')
            ->create(['email' => 'foundry@test.com']);

        $this->entityManager->refresh($user->_real());

        StaticDriver::rollBack();

        return 0;
    }

but if I do the same from behat context step:

    #[Given('/^user is created$/')]
    public function userIsCreated(): void
    {
        $user = UserFactory::new()
            ->password('test')
            ->create(['email' => 'foundry@test.com']);

        $this->entityManager->refresh($user->_real());
    }

I get an error:

Entity foundry@test.com is not managed. An entity is managed if its fetched from the database or registered as new through EntityManager#persist in...

Let me know if additional info is needed.
I would gladly propose a PR with a fix if someone would guide me towards the solution.

[nikophil]

Hi @much-rebel

I'm not using behat... The best would be to provide a small reproducer, this would greatly help with debugging
After the resolution, we might add a small non-regression test using behat in the CI

[nikophil]

Hey @much-rebel

I just thought a little bit more to this problem lately.

The problem is also the same than #750 where Factories trait was missing.

In this trait, we're booting Foundry with the right container.

I think, you should somehow call Configuration::boot() manually, in order to make things work correctly.

The real solution would be to create a Behat extension for Foundry. Some work has been started in the past (see this PR which was targeting Foundry v1). We would 100% be in favor of such a feature, but the problem is neither @kbond nor me have real experience with Behat.

[nikophil]

I'm closing this issue: I think you can fix the problem in userland by reproducing what is done in Factories trait in a subscriber or a BeforeScenario method.

As I said earlier the real solution would be to provide a Behat integration in Foundry. There is already an opened discussion here. PR are welcome for this :)