public function TextFieldTest::setUp in Zircon Profile 8

Same name in this branch

1. 8 core/modules/text/src/Tests/TextFieldTest.php \Drupal\text\Tests\TextFieldTest::setUp()
2. 8 core/modules/text/tests/src/Unit/Migrate/TextFieldTest.php \Drupal\Tests\text\Unit\Migrate\TextFieldTest::setUp()

Same name and namespace in other branches

1. 8.0 core/modules/text/tests/src/Unit/Migrate/TextFieldTest.php \Drupal\Tests\text\Unit\Migrate\TextFieldTest::setUp()

Overrides UnitTestCase::setUp

File

core/modules/text/tests/src/Unit/Migrate/TextFieldTest.php, line 35

Contains \Drupal\Tests\text\Unit\Migrate\TextFieldTest.

Class

TextFieldTest

@coversDefaultClass \Drupal\text\Plugin\migrate\cckfield\TextField @group text

Namespace

Drupal\Tests\text\Unit\Migrate

Code

public function setUp() {
  $this->plugin = new TextField([], 'text', []);
  $migration = $this
    ->prophesize(MigrationInterface::class);

  // The plugin's processCckFieldValues() method will call
  // setProcessOfProperty() and return nothing. So, in order to examine the
  // process pipeline created by the plugin, we need to ensure that
  // getProcess() always returns the last input to setProcessOfProperty().
  $migration
    ->setProcessOfProperty(Argument::type('string'), Argument::type('array'))
    ->will(function ($arguments) use ($migration) {
    $migration
      ->getProcess()
      ->willReturn($arguments[1]);
  });
  $this->migration = $migration
    ->reveal();
}