function ComposerPluginsValidatorInsecureTest::testAddDisallowedPlugin

Tests adding a plugin that's not allowed by the allow-plugins config.

The exception that this test looks for is not necessarily triggered by ComposerPluginsValidator; Composer will exit with an error if there is an installed plugin that is not allowed by the `allow-plugins` config. In practice, this means that whichever validator is the first one to do a Composer operation (via ComposerInspector) will get the exception -- it may or may not be ComposerPluginsValidator.

This test is here to ensure that Composer's behavior remains consistent, even if we're not explicitly testing ComposerPluginsValidator here.

File

core/modules/package_manager/tests/src/Kernel/ComposerPluginsValidatorInsecureTest.php, line 70

Class

ComposerPluginsValidatorInsecureTest

@covers \Drupal\package_manager\Validator\ComposerPluginsValidator[[api-linebreak]] @group package_manager @internal

Namespace

Code

public function testAddDisallowedPlugin() : void {
  $this->getStageFixtureManipulator()
    ->addPackage([
    'name' => 'composer/plugin-c',
    'version' => '16.4',
    'type' => 'composer-plugin',
    'require' => [
      'composer-plugin-api' => '*',
    ],
    'extra' => [
      'class' => 'AnyClass',
    ],
  ]);
  $expected_message = "composer/plugin-c contains a Composer plugin which is blocked by your allow-plugins config.";
  $stage = $this->createStage();
  $stage->create();
  $stage->require([
    'drupal/core:9.8.1',
  ]);
  try {
    // We are trying to add package plugin-c but not allowing it in config,
    // so we expect the operation to fail on PreApplyEvent.
    $stage->apply();
  } catch (SandboxEventException $e) {
    // Processing is required because the error message we get from Composer
    // contains multiple white spaces at the start or end of line.
    $this->assertStringContainsString($expected_message, preg_replace('/\\s\\s+/', '', $e->getMessage()));
    $this->assertInstanceOf(PreApplyEvent::class, $e->event);
  }
}