function ExternalCommandRequirementsTrait::checkMethodCommandRequirements

Same name in other branches
  1. 9 core/tests/Drupal/BuildTests/Framework/ExternalCommandRequirementsTrait.php \Drupal\BuildTests\Framework\ExternalCommandRequirementsTrait::checkMethodCommandRequirements()
  2. 10 core/tests/Drupal/BuildTests/Framework/ExternalCommandRequirementsTrait.php \Drupal\BuildTests\Framework\ExternalCommandRequirementsTrait::checkMethodCommandRequirements()

Checks whether required external commands are available per method.

Throws

\PHPUnit\Framework\SkippedTestError Thrown when the requirements are not met, and this test should be skipped. Callers should not catch this exception.

1 call to ExternalCommandRequirementsTrait::checkMethodCommandRequirements()
BuildTestBase::setUp in core/tests/Drupal/BuildTests/Framework/BuildTestBase.php

File

core/tests/Drupal/BuildTests/Framework/ExternalCommandRequirementsTrait.php, line 44

Class

ExternalCommandRequirementsTrait
Allows test classes to require external command line applications.

Namespace

Drupal\BuildTests\Framework

Code

private static function checkMethodCommandRequirements($name) {
    $annotations = Test::parseTestMethodAnnotations(static::class, $name);
    if (!empty($annotations['method']['requires'])) {
        static::checkExternalCommandRequirements($annotations['method']['requires']);
    }
}

Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.