function BuildTestBase::assertCommandSuccessful
Asserts that the last command ran without error.
This assertion checks whether the last command returned an exit code of 0.
If you need to assert a different exit code, then you can use executeCommand() and perform a different assertion on the process object.
9 calls to BuildTestBase::assertCommandSuccessful()
- BuildTestTest::testWorkspace in core/
tests/ Drupal/ BuildTests/ Framework/ Tests/ BuildTestTest.php  - Ensure that workspaces work.
 - ComponentsIsolatedBuildTest::testComponentComposerJson in core/
tests/ Drupal/ BuildTests/ Composer/ Component/ ComponentsIsolatedBuildTest.php  - Test whether components' composer.json can be installed in isolation.
 - ComponentsTaggedReleaseTest::testReleaseTagging in core/
tests/ Drupal/ BuildTests/ Composer/ Component/ ComponentsTaggedReleaseTest.php  - Validate release tagging and regeneration of dependencies.
 - ComposerBuildTestBase::assertDrupalVersion in core/
tests/ Drupal/ BuildTests/ Composer/ ComposerBuildTestBase.php  - Assert that the VERSION constant in Drupal.php is the expected value.
 - ComposerProjectTemplatesTest::makeVendorPackage in core/
tests/ Drupal/ BuildTests/ Composer/ Template/ ComposerProjectTemplatesTest.php  - Creates a test package that points to all the projects in vendor.
 
File
- 
              core/
tests/ Drupal/ BuildTests/ Framework/ BuildTestBase.php, line 296  
Class
- BuildTestBase
 - Provides a workspace to test build processes.
 
Namespace
Drupal\BuildTests\FrameworkCode
public function assertCommandSuccessful() {
  return $this->assertCommandExitCode(0);
}
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.