refactor: explicitly boot Foundry in ResetDatabase

[nikophil]

related to #1034

[nikophil]

@HypeMC would this do the trick?

[HypeMC]

@nikophil Thank you, I'll give it a try right away.

[HypeMC]

@nikophil Unfortunately, this change sees to break the following case:

class SomeTest extends WebTestCase
{
    use Factories;
    use ResetDatabase;

    public function testMyCode(): void
    {
        $client = self::createClient();

        // ...
    }

LogicException: Booting the kernel before calling "Symfony\Bundle\FrameworkBundle\Test\WebTestCase::createClient()" is not supported, the kernel should only be booted once.

[nikophil]

Damn... I'll add this use case to our test suite right now! A test using WebTestCase already exists, but it does not use ResetDatabase trait

[nikophil]

@HypeMC mind to test this new version, please?

I added a test to ensure ResetDatabase does not mess with self::createClient()

[HypeMC]

On it.

[HypeMC]

@nikophil Sadly, this reintroduces the original issue:

Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: The "kernel" service is synthetic, it needs to be set at boot time before it can be used.

[nikophil]

but the test you introduced in #993 is still green, we'll have to figure out why, I guess

[HypeMC]

I'll look into it tonight, and try to figure it out.

[nikophil]

super nice, thanks. Sorry to come back on this stuff but this would unlock an easy way to integrate Foundry with Behat, which is one of the next things I'd like to see in foundry

[HypeMC]

@nikophil Apologies for the late response, I couldn't find the time yesterday. Long story short, one test failed because it didn't use Factories. Once that was added, everything passed. So this fix is actually good. Thank you for investigating this and sorry for the false alert.

[nikophil]

ok thanks, this is very nice.

This kind of problem won't exist anymore once we have deprecated Factories trait 😄