Bug report: Conflict in kernel lifecycle for Symfony test.client and Symfony2Extension

[peterjmit]

When using this extension with the Mink integration, or using the test.client directly both this extension and the test.client try to manage the boot and/or shutdown of the kernel.

See:

• Symfony2Extension/src/Behat/Symfony2Extension/Context/Initializer/KernelAwareInitializer.php

  Lines 45 to 51 in 8263a47

  	public static function getSubscribedEvents()
  	{
  	return array(
  	ScenarioTested::AFTER => array('rebootKernel', -15),
  	ExampleTested::AFTER => array('rebootKernel', -15),
  	);
  	}

• https://github.com/symfony/FrameworkBundle/blob/3d6dd295fe3f323d93157ea9e9103cecfd78be19/Client.php#L99

This has two consequences.

1. Steps making a request cause the kernel to boot/shutdown (potential performance issue?)
2. Strange behaviour when injecting services into contexts. After a request is made, the service injected into the constructor is no longer the service that is being used by the kernel (because the container has been re-initialized.)

I am not sure if this is an issue, or something that can be realistically fixed. I experimented with preventing test.client from calling KernelInterface::shutdown however I ran into issues with sessions trying to re-initialize.

[sroze]

This was a known issue at this time, that is why Symfony's FrameworkBundle Client now have the ability to enable/disable reboot. Closing it.