protected function FileFieldTest::setUp in Drupal 10

Same name in this branch

1. 10 core/modules/file/tests/src/Unit/Plugin/migrate/field/d6/FileFieldTest.php \Drupal\Tests\file\Unit\Plugin\migrate\field\d6\FileFieldTest::setUp()
2. 10 core/modules/file/tests/src/Unit/Plugin/migrate/field/d7/FileFieldTest.php \Drupal\Tests\file\Unit\Plugin\migrate\field\d7\FileFieldTest::setUp()

Same name and namespace in other branches

1. 8 core/modules/file/tests/src/Unit/Plugin/migrate/field/d7/FileFieldTest.php \Drupal\Tests\file\Unit\Plugin\migrate\field\d7\FileFieldTest::setUp()
2. 9 core/modules/file/tests/src/Unit/Plugin/migrate/field/d7/FileFieldTest.php \Drupal\Tests\file\Unit\Plugin\migrate\field\d7\FileFieldTest::setUp()

Overrides UnitTestCase::setUp

File

core/modules/file/tests/src/Unit/Plugin/migrate/field/d7/FileFieldTest.php, line 32

Class

FileFieldTest

@coversDefaultClass \Drupal\file\Plugin\migrate\field\d7\FileField @group file

Namespace

Drupal\Tests\file\Unit\Plugin\migrate\field\d7

Code

protected function setUp() : void {
  $this->plugin = new FileField([], 'file', []);
  $migration = $this
    ->prophesize(MigrationInterface::class);

  // The plugin's defineValueProcessPipeline() method will call
  // mergeProcessOfProperty() 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 mergeProcessOfProperty().
  $migration
    ->mergeProcessOfProperty(Argument::type('string'), Argument::type('array'))
    ->will(function ($arguments) use ($migration) {
    $migration
      ->getProcess()
      ->willReturn($arguments[1]);
  });
  $this->migration = $migration
    ->reveal();
}