function ExternalCommandRequirementTest::testCheckExternalCommandRequirementsAvailable

Same name and namespace in other branches
  1. 8.9.x core/tests/Drupal/BuildTests/Framework/Tests/ExternalCommandRequirementTest.php \Drupal\BuildTests\Framework\Tests\ExternalCommandRequirementTest::testCheckExternalCommandRequirementsAvailable()
  2. 10 core/tests/Drupal/BuildTests/Framework/Tests/ExternalCommandRequirementTest.php \Drupal\BuildTests\Framework\Tests\ExternalCommandRequirementTest::testCheckExternalCommandRequirementsAvailable()

@covers ::checkExternalCommandRequirements

File

core/tests/Drupal/BuildTests/Framework/Tests/ExternalCommandRequirementTest.php, line 39

Class

ExternalCommandRequirementTest
@coversDefaultClass \Drupal\BuildTests\Framework\ExternalCommandRequirementsTrait[[api-linebreak]] @group Build

Namespace

Drupal\BuildTests\Framework\Tests

Code

public function testCheckExternalCommandRequirementsAvailable() {
  $requires = new UsesCommandRequirements();
  $ref_check_requirements = new \ReflectionMethod($requires, 'checkExternalCommandRequirements');
  $ref_check_requirements->setAccessible(TRUE);
  // Use a try/catch block because otherwise PHPUnit might think this test is
  // legitimately skipped.
  try {
    $this->assertNull($ref_check_requirements->invokeArgs($requires, [
      [
        'externalCommand available_command',
      ],
    ]));
  } catch (SkippedTestError $exception) {
    $this->fail(sprintf('The external command should be available: %s', $exception->getMessage()));
  }
}

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