Skip to content
Snippets Groups Projects
Commit ff67d004 authored by Kunal Sachdev's avatar Kunal Sachdev Committed by Wim Leers
Browse files

Issue #3356640 by kunal.sachdev, phenaproxima, Wim Leers: Explain why...

Issue #3356640 by kunal.sachdev, phenaproxima, Wim Leers: Explain why ComposerPluginsValidatorTest::testAddDisallowedPlugin() exists, even if it is not directly testing ComposerPluginsValidator
parent 84cc874b
No related branches found
No related tags found
No related merge requests found
......@@ -104,6 +104,16 @@ class ComposerPluginsValidatorTest extends PackageManagerKernelTestBase {
/**
* 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.
*/
public function testAddDisallowedPlugin(): void {
$this->getStageFixtureManipulator()
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment